Mixing
![Should I list a job on my resume when I didn't pass the trial period and only lasted 4 weeks? [duplicate]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjbpfN9tAutmK93bJRC3ZoROZzi2TJDms5n8_qJuhgE0a9b52OOHayv3NGT8igAdFL7byXNst-_1DZK5SjrIJ28_6RQPUpBROqMs5s6jo-ZsjX8kjDwfxJufIitH3TaQRXWaGSQKRQib-f/s72-c/1.jpg)
Working 2 full time software jobs? [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
2
down vote
favorite
I'm interested in working 2 full time positions at two different companies. The first company is the company I am already working full time and salaried. The workload is laid-back and not super intensive. The hours are flexible and I am 1 of 2 developers working on one single project as a part of a 5 year contract (the company has a contract with a client). The supervisor isn't strict on our hours, however I do respect their time.
There is a new company that is interested in me. I have interviewed with them during my lunch break. They are fully aware that I have a full time position already. They still wanted to interview me. They have mentioned that their manager would not mind that I am fully employed. I am taking this to mean that it is a strong possibility that I can work at this company that I am interviewing for as a full time developer and the company I am already working for.
From what I understand about the new company I have interviewed, their workload is based on developing apps from the ground up. Their workload is more volatile than the company I am already working for. I am open to this. They are interested in hiring a server-side developer, but they want someone who is willing to edify themselves in areas outside of their expertise (this may include going to conferences and learning from other developers). I am open to this.
After the interview with this new company, they asked me if I am still interested in continuing the interview process. I told them I will have to consider continuing the interview process. I plan on giving them an answer Monday.
Does anyone have any advice for me? I am very interested in working for both companies. I am aware of the workload and I do understand the environment.
Thanks,
Justin
software-industry career-development job-offer new-job work-experience
asked Mar 12 '16 at 4:16
jwyatt123
2212
closed as off-topic by gnat, The Wandering Dev Manager, Dawny33, HopelessN00b, Lilienthal♦ Mar 12 '16 at 21:35
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – gnat, The Wandering Dev Manager, Dawny33, HopelessN00b, Lilienthal
suggest improvements |Â
up vote
2
down vote
favorite
I'm interested in working 2 full time positions at two different companies. The first company is the company I am already working full time and salaried. The workload is laid-back and not super intensive. The hours are flexible and I am 1 of 2 developers working on one single project as a part of a 5 year contract (the company has a contract with a client). The supervisor isn't strict on our hours, however I do respect their time.
There is a new company that is interested in me. I have interviewed with them during my lunch break. They are fully aware that I have a full time position already. They still wanted to interview me. They have mentioned that their manager would not mind that I am fully employed. I am taking this to mean that it is a strong possibility that I can work at this company that I am interviewing for as a full time developer and the company I am already working for.
From what I understand about the new company I have interviewed, their workload is based on developing apps from the ground up. Their workload is more volatile than the company I am already working for. I am open to this. They are interested in hiring a server-side developer, but they want someone who is willing to edify themselves in areas outside of their expertise (this may include going to conferences and learning from other developers). I am open to this.
After the interview with this new company, they asked me if I am still interested in continuing the interview process. I told them I will have to consider continuing the interview process. I plan on giving them an answer Monday.
Does anyone have any advice for me? I am very interested in working for both companies. I am aware of the workload and I do understand the environment.
Thanks,
Justin
software-industry career-development job-offer new-job work-experience
asked Mar 12 '16 at 4:16
jwyatt123
2212
closed as off-topic by gnat, The Wandering Dev Manager, Dawny33, HopelessN00b, Lilienthal♦ Mar 12 '16 at 21:35
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – gnat, The Wandering Dev Manager, Dawny33, HopelessN00b, Lilienthal
4
80 hours/ week of coding is absolutely brutal. My workweek varies in length between 45 and 60 hours. I've hit 80 a couple of times and it is absolutely not sustainable. It's 16 hours a day, only leaving 8 to sleep, eat, commute, bathe. Nevermind having time for a life or hobbies. Additionally, you are definitely going to see decrease in productivity for those extra hours. Not worth it, imo.
– user5621
Mar 12 '16 at 13:22
What happens when one of the two jobs undergoes "crunch time" and requires you to work a lot of overtime to solve an emergency?
– Moo
Mar 12 '16 at 14:34
Working two devs jobs? After Wednesday your productivity is going to drop to about 0, and it probably won't be too long until you realize why people don't generally work 2 full time jobs, unless it's absolutely necessary.
– HopelessN00b
Mar 12 '16 at 19:27
A: there is no question here (VTC), B: you are almost certainly interpreting the comments of the second company incorrectly, C: there is no way your current company will agree with this and they'll probably fire you when they find out, D: how do you even see the logistics here?
– Lilienthal♦
Mar 12 '16 at 21:40
1
This is a previous question asking the same thing - workplace.stackexchange.com/q/16698/2322
– Elysian Fields♦
Mar 12 '16 at 21:45
suggest improvements |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I'm interested in working 2 full time positions at two different companies. The first company is the company I am already working full time and salaried. The workload is laid-back and not super intensive. The hours are flexible and I am 1 of 2 developers working on one single project as a part of a 5 year contract (the company has a contract with a client). The supervisor isn't strict on our hours, however I do respect their time.
There is a new company that is interested in me. I have interviewed with them during my lunch break. They are fully aware that I have a full time position already. They still wanted to interview me. They have mentioned that their manager would not mind that I am fully employed. I am taking this to mean that it is a strong possibility that I can work at this company that I am interviewing for as a full time developer and the company I am already working for.
From what I understand about the new company I have interviewed, their workload is based on developing apps from the ground up. Their workload is more volatile than the company I am already working for. I am open to this. They are interested in hiring a server-side developer, but they want someone who is willing to edify themselves in areas outside of their expertise (this may include going to conferences and learning from other developers). I am open to this.
After the interview with this new company, they asked me if I am still interested in continuing the interview process. I told them I will have to consider continuing the interview process. I plan on giving them an answer Monday.
Does anyone have any advice for me? I am very interested in working for both companies. I am aware of the workload and I do understand the environment.
Thanks,
Justin
software-industry career-development job-offer new-job work-experience
asked Mar 12 '16 at 4:16
jwyatt123
2212
I'm interested in working 2 full time positions at two different companies. The first company is the company I am already working full time and salaried. The workload is laid-back and not super intensive. The hours are flexible and I am 1 of 2 developers working on one single project as a part of a 5 year contract (the company has a contract with a client). The supervisor isn't strict on our hours, however I do respect their time.
There is a new company that is interested in me. I have interviewed with them during my lunch break. They are fully aware that I have a full time position already. They still wanted to interview me. They have mentioned that their manager would not mind that I am fully employed. I am taking this to mean that it is a strong possibility that I can work at this company that I am interviewing for as a full time developer and the company I am already working for.
From what I understand about the new company I have interviewed, their workload is based on developing apps from the ground up. Their workload is more volatile than the company I am already working for. I am open to this. They are interested in hiring a server-side developer, but they want someone who is willing to edify themselves in areas outside of their expertise (this may include going to conferences and learning from other developers). I am open to this.
After the interview with this new company, they asked me if I am still interested in continuing the interview process. I told them I will have to consider continuing the interview process. I plan on giving them an answer Monday.
Does anyone have any advice for me? I am very interested in working for both companies. I am aware of the workload and I do understand the environment.
Thanks,
Justin
software-industry career-development job-offer new-job work-experience
asked Mar 12 '16 at 4:16
jwyatt123
2212
asked Mar 12 '16 at 4:16
jwyatt123
2212
asked Mar 12 '16 at 4:16
jwyatt123
2212
asked Mar 12 '16 at 4:16
jwyatt123
2212
2212
closed as off-topic by gnat, The Wandering Dev Manager, Dawny33, HopelessN00b, Lilienthal♦ Mar 12 '16 at 21:35
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – gnat, The Wandering Dev Manager, Dawny33, HopelessN00b, Lilienthal
closed as off-topic by gnat, The Wandering Dev Manager, Dawny33, HopelessN00b, Lilienthal♦ Mar 12 '16 at 21:35
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – gnat, The Wandering Dev Manager, Dawny33, HopelessN00b, Lilienthal
4
80 hours/ week of coding is absolutely brutal. My workweek varies in length between 45 and 60 hours. I've hit 80 a couple of times and it is absolutely not sustainable. It's 16 hours a day, only leaving 8 to sleep, eat, commute, bathe. Nevermind having time for a life or hobbies. Additionally, you are definitely going to see decrease in productivity for those extra hours. Not worth it, imo.
– user5621
Mar 12 '16 at 13:22
What happens when one of the two jobs undergoes "crunch time" and requires you to work a lot of overtime to solve an emergency?
– Moo
Mar 12 '16 at 14:34
Working two devs jobs? After Wednesday your productivity is going to drop to about 0, and it probably won't be too long until you realize why people don't generally work 2 full time jobs, unless it's absolutely necessary.
– HopelessN00b
Mar 12 '16 at 19:27
A: there is no question here (VTC), B: you are almost certainly interpreting the comments of the second company incorrectly, C: there is no way your current company will agree with this and they'll probably fire you when they find out, D: how do you even see the logistics here?
– Lilienthal♦
Mar 12 '16 at 21:40
1
This is a previous question asking the same thing - workplace.stackexchange.com/q/16698/2322
– Elysian Fields♦
Mar 12 '16 at 21:45
suggest improvements |Â
4
80 hours/ week of coding is absolutely brutal. My workweek varies in length between 45 and 60 hours. I've hit 80 a couple of times and it is absolutely not sustainable. It's 16 hours a day, only leaving 8 to sleep, eat, commute, bathe. Nevermind having time for a life or hobbies. Additionally, you are definitely going to see decrease in productivity for those extra hours. Not worth it, imo.
– user5621
Mar 12 '16 at 13:22
What happens when one of the two jobs undergoes "crunch time" and requires you to work a lot of overtime to solve an emergency?
– Moo
Mar 12 '16 at 14:34
Working two devs jobs? After Wednesday your productivity is going to drop to about 0, and it probably won't be too long until you realize why people don't generally work 2 full time jobs, unless it's absolutely necessary.
– HopelessN00b
Mar 12 '16 at 19:27
A: there is no question here (VTC), B: you are almost certainly interpreting the comments of the second company incorrectly, C: there is no way your current company will agree with this and they'll probably fire you when they find out, D: how do you even see the logistics here?
– Lilienthal♦
Mar 12 '16 at 21:40
1
This is a previous question asking the same thing - workplace.stackexchange.com/q/16698/2322
– Elysian Fields♦
Mar 12 '16 at 21:45
4
4
80 hours/ week of coding is absolutely brutal. My workweek varies in length between 45 and 60 hours. I've hit 80 a couple of times and it is absolutely not sustainable. It's 16 hours a day, only leaving 8 to sleep, eat, commute, bathe. Nevermind having time for a life or hobbies. Additionally, you are definitely going to see decrease in productivity for those extra hours. Not worth it, imo.
– user5621
Mar 12 '16 at 13:22
80 hours/ week of coding is absolutely brutal. My workweek varies in length between 45 and 60 hours. I've hit 80 a couple of times and it is absolutely not sustainable. It's 16 hours a day, only leaving 8 to sleep, eat, commute, bathe. Nevermind having time for a life or hobbies. Additionally, you are definitely going to see decrease in productivity for those extra hours. Not worth it, imo.
– user5621
Mar 12 '16 at 13:22
What happens when one of the two jobs undergoes "crunch time" and requires you to work a lot of overtime to solve an emergency?
– Moo
Mar 12 '16 at 14:34
What happens when one of the two jobs undergoes "crunch time" and requires you to work a lot of overtime to solve an emergency?
– Moo
Mar 12 '16 at 14:34
Working two devs jobs? After Wednesday your productivity is going to drop to about 0, and it probably won't be too long until you realize why people don't generally work 2 full time jobs, unless it's absolutely necessary.
– HopelessN00b
Mar 12 '16 at 19:27
Working two devs jobs? After Wednesday your productivity is going to drop to about 0, and it probably won't be too long until you realize why people don't generally work 2 full time jobs, unless it's absolutely necessary.
– HopelessN00b
Mar 12 '16 at 19:27
A: there is no question here (VTC), B: you are almost certainly interpreting the comments of the second company incorrectly, C: there is no way your current company will agree with this and they'll probably fire you when they find out, D: how do you even see the logistics here?
– Lilienthal♦
Mar 12 '16 at 21:40
A: there is no question here (VTC), B: you are almost certainly interpreting the comments of the second company incorrectly, C: there is no way your current company will agree with this and they'll probably fire you when they find out, D: how do you even see the logistics here?
– Lilienthal♦
Mar 12 '16 at 21:40
1
1
This is a previous question asking the same thing - workplace.stackexchange.com/q/16698/2322
– Elysian Fields♦
Mar 12 '16 at 21:45
This is a previous question asking the same thing - workplace.stackexchange.com/q/16698/2322
– Elysian Fields♦
Mar 12 '16 at 21:45
suggest improvements |Â
3 Answers
3
active
oldest
votes
up vote
9
down vote
There are two big issues that I see here:
You say you are "aware of the workload", but have you really tried working 80, 90, 100 hours a week on a regular basis? My experience with development in general is that even the "laid back" places aren't going to be happy if you put in 30 hours of effort and are only able to increase it to 40 or so when they need you the most.
It's also my experience that even 80 hours a week is a lot of time to work. A lot of people can handle it for a couple months, but if you're actually wanting to be a FTE at this other place, it's not likely going to be for just a couple months, is it? Burnout is a real thing, even if you're doing something you love. In fact, in some ways it's much worse when you're doing something you love doing because you'll begin to hate it.
You really should make sure that moonlighting is a thing that isn't a breach of your contract with your first company, because a lot of the time companies will put people such as yourself on salary instead of hourly wages because they want all of your attention focused on them. Even if there's nothing in there expressly against it, they might have a completely different, less laid back attitude towards you if, instead of giving them the best 30-40 hours of your week, you give them the worst 30-40 hours.
Reading between the lines, what this really sounds like is that the second company does stuff that seems more exciting to you but your current job gives you a paycheck you can count on, so you want both. Unfortunately, you can't always have everything that you want and I think this is going to end up being one of those times. At the same time, if you think you're going to like the other job better, why not take the leap? Perhaps try and find a way to make a gracious exit from the first place, because usually the development industry in a given city is small and you don't want to burn bridges (and hey, worst case scenario, maybe you can get the old job back if the new one doesn't work out).
I just think that what you seem to be angling for as a "compromise" is going to be a solution that leaves nobody happy, least of all yourself.
answered Mar 12 '16 at 5:13
NotVonKaiser
6,5051533
Thank you for your advise. I will consider take this into consideration.
– jwyatt123
Mar 12 '16 at 5:27
suggest improvements |Â
up vote
2
down vote
Generally, if you are a salaried world, you have signed a contract saying that your employer has rights to all your creative output in any field vaguely emboloc [darned autocorrect, that was supposed to be "related to the"] one they do business in. Unless you have explicitly discussed it with them and gotten permission, you may not even be able to do noncommercial or open source work.
So the option probably doesn't exist. But you can investigate it.
answered Mar 12 '16 at 4:25
keshlam
41.5k1267144
What is 'vaguely embolic' supposed to mean here?
– Deer Hunter
Mar 12 '16 at 8:05
Thanks, typo fixed. Good thing about gestural typing is that it's much faster, bad thing is that it does some creative writing of its own. :-J
– keshlam
Mar 12 '16 at 16:29
suggest improvements |Â
up vote
1
down vote
Two full time jobs, plus whatever commute is needed, is going to kill you. Plus get you fired twice when you can't keep up with your duties in either job.
If you want to kill yourself, first check that your contract with the first company allows you to work elsewhere at all. Second, you said the second company is aware that you have a fulltime job. Are they aware that you want to keep working in that full-time job? They probably assume that you are going to quit your old job.
And there's a quote: "You can make people be at work for 80 hours a week. You can't make them work for more than 40 hours a week". Both your employers would notice that quite quickly.
answered Mar 12 '16 at 14:10
gnasher729
70.8k31131222
suggest improvements |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
9
down vote
There are two big issues that I see here:
You say you are "aware of the workload", but have you really tried working 80, 90, 100 hours a week on a regular basis? My experience with development in general is that even the "laid back" places aren't going to be happy if you put in 30 hours of effort and are only able to increase it to 40 or so when they need you the most.
It's also my experience that even 80 hours a week is a lot of time to work. A lot of people can handle it for a couple months, but if you're actually wanting to be a FTE at this other place, it's not likely going to be for just a couple months, is it? Burnout is a real thing, even if you're doing something you love. In fact, in some ways it's much worse when you're doing something you love doing because you'll begin to hate it.
You really should make sure that moonlighting is a thing that isn't a breach of your contract with your first company, because a lot of the time companies will put people such as yourself on salary instead of hourly wages because they want all of your attention focused on them. Even if there's nothing in there expressly against it, they might have a completely different, less laid back attitude towards you if, instead of giving them the best 30-40 hours of your week, you give them the worst 30-40 hours.
Reading between the lines, what this really sounds like is that the second company does stuff that seems more exciting to you but your current job gives you a paycheck you can count on, so you want both. Unfortunately, you can't always have everything that you want and I think this is going to end up being one of those times. At the same time, if you think you're going to like the other job better, why not take the leap? Perhaps try and find a way to make a gracious exit from the first place, because usually the development industry in a given city is small and you don't want to burn bridges (and hey, worst case scenario, maybe you can get the old job back if the new one doesn't work out).
I just think that what you seem to be angling for as a "compromise" is going to be a solution that leaves nobody happy, least of all yourself.
answered Mar 12 '16 at 5:13
NotVonKaiser
6,5051533
Thank you for your advise. I will consider take this into consideration.
– jwyatt123
Mar 12 '16 at 5:27
suggest improvements |Â
up vote
9
down vote
There are two big issues that I see here:
You say you are "aware of the workload", but have you really tried working 80, 90, 100 hours a week on a regular basis? My experience with development in general is that even the "laid back" places aren't going to be happy if you put in 30 hours of effort and are only able to increase it to 40 or so when they need you the most.
It's also my experience that even 80 hours a week is a lot of time to work. A lot of people can handle it for a couple months, but if you're actually wanting to be a FTE at this other place, it's not likely going to be for just a couple months, is it? Burnout is a real thing, even if you're doing something you love. In fact, in some ways it's much worse when you're doing something you love doing because you'll begin to hate it.
You really should make sure that moonlighting is a thing that isn't a breach of your contract with your first company, because a lot of the time companies will put people such as yourself on salary instead of hourly wages because they want all of your attention focused on them. Even if there's nothing in there expressly against it, they might have a completely different, less laid back attitude towards you if, instead of giving them the best 30-40 hours of your week, you give them the worst 30-40 hours.
Reading between the lines, what this really sounds like is that the second company does stuff that seems more exciting to you but your current job gives you a paycheck you can count on, so you want both. Unfortunately, you can't always have everything that you want and I think this is going to end up being one of those times. At the same time, if you think you're going to like the other job better, why not take the leap? Perhaps try and find a way to make a gracious exit from the first place, because usually the development industry in a given city is small and you don't want to burn bridges (and hey, worst case scenario, maybe you can get the old job back if the new one doesn't work out).
I just think that what you seem to be angling for as a "compromise" is going to be a solution that leaves nobody happy, least of all yourself.
answered Mar 12 '16 at 5:13
NotVonKaiser
6,5051533
Thank you for your advise. I will consider take this into consideration.
– jwyatt123
Mar 12 '16 at 5:27
suggest improvements |Â
up vote
9
down vote
up vote
9
down vote
There are two big issues that I see here:
You say you are "aware of the workload", but have you really tried working 80, 90, 100 hours a week on a regular basis? My experience with development in general is that even the "laid back" places aren't going to be happy if you put in 30 hours of effort and are only able to increase it to 40 or so when they need you the most.
It's also my experience that even 80 hours a week is a lot of time to work. A lot of people can handle it for a couple months, but if you're actually wanting to be a FTE at this other place, it's not likely going to be for just a couple months, is it? Burnout is a real thing, even if you're doing something you love. In fact, in some ways it's much worse when you're doing something you love doing because you'll begin to hate it.
You really should make sure that moonlighting is a thing that isn't a breach of your contract with your first company, because a lot of the time companies will put people such as yourself on salary instead of hourly wages because they want all of your attention focused on them. Even if there's nothing in there expressly against it, they might have a completely different, less laid back attitude towards you if, instead of giving them the best 30-40 hours of your week, you give them the worst 30-40 hours.
Reading between the lines, what this really sounds like is that the second company does stuff that seems more exciting to you but your current job gives you a paycheck you can count on, so you want both. Unfortunately, you can't always have everything that you want and I think this is going to end up being one of those times. At the same time, if you think you're going to like the other job better, why not take the leap? Perhaps try and find a way to make a gracious exit from the first place, because usually the development industry in a given city is small and you don't want to burn bridges (and hey, worst case scenario, maybe you can get the old job back if the new one doesn't work out).
I just think that what you seem to be angling for as a "compromise" is going to be a solution that leaves nobody happy, least of all yourself.
answered Mar 12 '16 at 5:13
NotVonKaiser
6,5051533
There are two big issues that I see here:
You say you are "aware of the workload", but have you really tried working 80, 90, 100 hours a week on a regular basis? My experience with development in general is that even the "laid back" places aren't going to be happy if you put in 30 hours of effort and are only able to increase it to 40 or so when they need you the most.
It's also my experience that even 80 hours a week is a lot of time to work. A lot of people can handle it for a couple months, but if you're actually wanting to be a FTE at this other place, it's not likely going to be for just a couple months, is it? Burnout is a real thing, even if you're doing something you love. In fact, in some ways it's much worse when you're doing something you love doing because you'll begin to hate it.
You really should make sure that moonlighting is a thing that isn't a breach of your contract with your first company, because a lot of the time companies will put people such as yourself on salary instead of hourly wages because they want all of your attention focused on them. Even if there's nothing in there expressly against it, they might have a completely different, less laid back attitude towards you if, instead of giving them the best 30-40 hours of your week, you give them the worst 30-40 hours.
Reading between the lines, what this really sounds like is that the second company does stuff that seems more exciting to you but your current job gives you a paycheck you can count on, so you want both. Unfortunately, you can't always have everything that you want and I think this is going to end up being one of those times. At the same time, if you think you're going to like the other job better, why not take the leap? Perhaps try and find a way to make a gracious exit from the first place, because usually the development industry in a given city is small and you don't want to burn bridges (and hey, worst case scenario, maybe you can get the old job back if the new one doesn't work out).
I just think that what you seem to be angling for as a "compromise" is going to be a solution that leaves nobody happy, least of all yourself.
answered Mar 12 '16 at 5:13
NotVonKaiser
6,5051533
answered Mar 12 '16 at 5:13
NotVonKaiser
6,5051533
answered Mar 12 '16 at 5:13
NotVonKaiser
6,5051533
answered Mar 12 '16 at 5:13
NotVonKaiser
6,5051533
6,5051533
Thank you for your advise. I will consider take this into consideration.
– jwyatt123
Mar 12 '16 at 5:27
suggest improvements |Â
Thank you for your advise. I will consider take this into consideration.
– jwyatt123
Mar 12 '16 at 5:27
Thank you for your advise. I will consider take this into consideration.
– jwyatt123
Mar 12 '16 at 5:27
Thank you for your advise. I will consider take this into consideration.
– jwyatt123
Mar 12 '16 at 5:27
suggest improvements |Â
up vote
2
down vote
Generally, if you are a salaried world, you have signed a contract saying that your employer has rights to all your creative output in any field vaguely emboloc [darned autocorrect, that was supposed to be "related to the"] one they do business in. Unless you have explicitly discussed it with them and gotten permission, you may not even be able to do noncommercial or open source work.
So the option probably doesn't exist. But you can investigate it.
answered Mar 12 '16 at 4:25
keshlam
41.5k1267144
What is 'vaguely embolic' supposed to mean here?
– Deer Hunter
Mar 12 '16 at 8:05
Thanks, typo fixed. Good thing about gestural typing is that it's much faster, bad thing is that it does some creative writing of its own. :-J
– keshlam
Mar 12 '16 at 16:29
suggest improvements |Â
up vote
2
down vote
Generally, if you are a salaried world, you have signed a contract saying that your employer has rights to all your creative output in any field vaguely emboloc [darned autocorrect, that was supposed to be "related to the"] one they do business in. Unless you have explicitly discussed it with them and gotten permission, you may not even be able to do noncommercial or open source work.
So the option probably doesn't exist. But you can investigate it.
answered Mar 12 '16 at 4:25
keshlam
41.5k1267144
What is 'vaguely embolic' supposed to mean here?
– Deer Hunter
Mar 12 '16 at 8:05
Thanks, typo fixed. Good thing about gestural typing is that it's much faster, bad thing is that it does some creative writing of its own. :-J
– keshlam
Mar 12 '16 at 16:29
suggest improvements |Â
up vote
2
down vote
up vote
2
down vote
Generally, if you are a salaried world, you have signed a contract saying that your employer has rights to all your creative output in any field vaguely emboloc [darned autocorrect, that was supposed to be "related to the"] one they do business in. Unless you have explicitly discussed it with them and gotten permission, you may not even be able to do noncommercial or open source work.
So the option probably doesn't exist. But you can investigate it.
answered Mar 12 '16 at 4:25
keshlam
41.5k1267144
Generally, if you are a salaried world, you have signed a contract saying that your employer has rights to all your creative output in any field vaguely emboloc [darned autocorrect, that was supposed to be "related to the"] one they do business in. Unless you have explicitly discussed it with them and gotten permission, you may not even be able to do noncommercial or open source work.
So the option probably doesn't exist. But you can investigate it.
answered Mar 12 '16 at 4:25
keshlam
41.5k1267144
edited Mar 12 '16 at 16:27
answered Mar 12 '16 at 4:25
keshlam
41.5k1267144
answered Mar 12 '16 at 4:25
keshlam
41.5k1267144
answered Mar 12 '16 at 4:25
keshlam
41.5k1267144
41.5k1267144
What is 'vaguely embolic' supposed to mean here?
– Deer Hunter
Mar 12 '16 at 8:05
Thanks, typo fixed. Good thing about gestural typing is that it's much faster, bad thing is that it does some creative writing of its own. :-J
– keshlam
Mar 12 '16 at 16:29
suggest improvements |Â
What is 'vaguely embolic' supposed to mean here?
– Deer Hunter
Mar 12 '16 at 8:05
Thanks, typo fixed. Good thing about gestural typing is that it's much faster, bad thing is that it does some creative writing of its own. :-J
– keshlam
Mar 12 '16 at 16:29
What is 'vaguely embolic' supposed to mean here?
– Deer Hunter
Mar 12 '16 at 8:05
What is 'vaguely embolic' supposed to mean here?
– Deer Hunter
Mar 12 '16 at 8:05
Thanks, typo fixed. Good thing about gestural typing is that it's much faster, bad thing is that it does some creative writing of its own. :-J
– keshlam
Mar 12 '16 at 16:29
Thanks, typo fixed. Good thing about gestural typing is that it's much faster, bad thing is that it does some creative writing of its own. :-J
– keshlam
Mar 12 '16 at 16:29
suggest improvements |Â
up vote
1
down vote
Two full time jobs, plus whatever commute is needed, is going to kill you. Plus get you fired twice when you can't keep up with your duties in either job.
If you want to kill yourself, first check that your contract with the first company allows you to work elsewhere at all. Second, you said the second company is aware that you have a fulltime job. Are they aware that you want to keep working in that full-time job? They probably assume that you are going to quit your old job.
And there's a quote: "You can make people be at work for 80 hours a week. You can't make them work for more than 40 hours a week". Both your employers would notice that quite quickly.
answered Mar 12 '16 at 14:10
gnasher729
70.8k31131222
suggest improvements |Â
up vote
1
down vote
Two full time jobs, plus whatever commute is needed, is going to kill you. Plus get you fired twice when you can't keep up with your duties in either job.
If you want to kill yourself, first check that your contract with the first company allows you to work elsewhere at all. Second, you said the second company is aware that you have a fulltime job. Are they aware that you want to keep working in that full-time job? They probably assume that you are going to quit your old job.
And there's a quote: "You can make people be at work for 80 hours a week. You can't make them work for more than 40 hours a week". Both your employers would notice that quite quickly.
answered Mar 12 '16 at 14:10
gnasher729
70.8k31131222
suggest improvements |Â
up vote
1
down vote
up vote
1
down vote
Two full time jobs, plus whatever commute is needed, is going to kill you. Plus get you fired twice when you can't keep up with your duties in either job.
If you want to kill yourself, first check that your contract with the first company allows you to work elsewhere at all. Second, you said the second company is aware that you have a fulltime job. Are they aware that you want to keep working in that full-time job? They probably assume that you are going to quit your old job.
And there's a quote: "You can make people be at work for 80 hours a week. You can't make them work for more than 40 hours a week". Both your employers would notice that quite quickly.
answered Mar 12 '16 at 14:10
gnasher729
70.8k31131222
Two full time jobs, plus whatever commute is needed, is going to kill you. Plus get you fired twice when you can't keep up with your duties in either job.
If you want to kill yourself, first check that your contract with the first company allows you to work elsewhere at all. Second, you said the second company is aware that you have a fulltime job. Are they aware that you want to keep working in that full-time job? They probably assume that you are going to quit your old job.
And there's a quote: "You can make people be at work for 80 hours a week. You can't make them work for more than 40 hours a week". Both your employers would notice that quite quickly.
answered Mar 12 '16 at 14:10
gnasher729
70.8k31131222
answered Mar 12 '16 at 14:10
gnasher729
70.8k31131222
answered Mar 12 '16 at 14:10
gnasher729
70.8k31131222
answered Mar 12 '16 at 14:10
gnasher729
70.8k31131222
70.8k31131222
suggest improvements |Â
suggest improvements |Â
4
80 hours/ week of coding is absolutely brutal. My workweek varies in length between 45 and 60 hours. I've hit 80 a couple of times and it is absolutely not sustainable. It's 16 hours a day, only leaving 8 to sleep, eat, commute, bathe. Nevermind having time for a life or hobbies. Additionally, you are definitely going to see decrease in productivity for those extra hours. Not worth it, imo.
– user5621
Mar 12 '16 at 13:22
What happens when one of the two jobs undergoes "crunch time" and requires you to work a lot of overtime to solve an emergency?
– Moo
Mar 12 '16 at 14:34
Working two devs jobs? After Wednesday your productivity is going to drop to about 0, and it probably won't be too long until you realize why people don't generally work 2 full time jobs, unless it's absolutely necessary.
– HopelessN00b
Mar 12 '16 at 19:27
A: there is no question here (VTC), B: you are almost certainly interpreting the comments of the second company incorrectly, C: there is no way your current company will agree with this and they'll probably fire you when they find out, D: how do you even see the logistics here?
– Lilienthal♦
Mar 12 '16 at 21:40
1
This is a previous question asking the same thing - workplace.stackexchange.com/q/16698/2322
– Elysian Fields♦
Mar 12 '16 at 21:45