Humanist living the Colorado life, w/ a modicum of scripting experience. My background is across multiple industries (mostly contract work). Emotional intelligence > Artificial Intelligence
Pauline, I think it really matters on the company/culture.
I've worked with devs who seem very happy and accomplished in their work. At other times, I've worked with devs who were swamped with moving targets and strict, non-technical, upper management who added gas to the fire.
The biggest factor to me is probably flexibility to WFH. I have had work in the past where remote work was not an option. I now have 1 day per week where we can work remote and it does make a difference (Enough so that I would negotiate any future offers based not on salary, but on working from home weekly)
Yes.. I remember early in my career I went as an intern to Big Company A. I was lucky to go to a team full with almost 100% senior developers. When talking to each one of them I asked them if they still liked programming, and all of them told me they were fed up with it and couldn't wait to move on.
That was shocking to me.. and made me have some existential doubts.
Later I interned at Medium Company B. And at this company I asked the senior developers if they liked to program. And they couldn't even understand why I would ask such a thing. They obviously liked it.
There were huge cultural differences between A and B. A was manager driven, lots of middle management making you feel small all the time and subject to the whims of people that just didn't get it. Company B was a totally flat structure, even though they had hundreds of people in the company. Its environment was totally enviable. A great company to work for.
So yeah.. I'd say company culture is very important.
If you're stuck in the wrong culture you just want to die.
I agree with this, company and culture definitely play a critical role. Lack of communication, unreasonable deadlines, and unclear expectations will turn into burnout real quick. However, the power to create something from nothing can be really rewarding.
If you are interested and engaged with what you are working on, then you'll probably be happy. This isn't always the case though, since maintaining old legacy code is usually something all devs deal with at some point in their career. For me, I enjoy starting fresh and using the latest and greatest stack, but dealing with old and outdated technical debt always rears its ugly head.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Pauline, I think it really matters on the company/culture.
I've worked with devs who seem very happy and accomplished in their work. At other times, I've worked with devs who were swamped with moving targets and strict, non-technical, upper management who added gas to the fire.
The biggest factor to me is probably flexibility to WFH. I have had work in the past where remote work was not an option. I now have 1 day per week where we can work remote and it does make a difference (Enough so that I would negotiate any future offers based not on salary, but on working from home weekly)
What do you think?
Yes.. I remember early in my career I went as an intern to Big Company A. I was lucky to go to a team full with almost 100% senior developers. When talking to each one of them I asked them if they still liked programming, and all of them told me they were fed up with it and couldn't wait to move on.
That was shocking to me.. and made me have some existential doubts.
Later I interned at Medium Company B. And at this company I asked the senior developers if they liked to program. And they couldn't even understand why I would ask such a thing. They obviously liked it.
There were huge cultural differences between A and B. A was manager driven, lots of middle management making you feel small all the time and subject to the whims of people that just didn't get it. Company B was a totally flat structure, even though they had hundreds of people in the company. Its environment was totally enviable. A great company to work for.
So yeah.. I'd say company culture is very important.
If you're stuck in the wrong culture you just want to die.
I agree with this, company and culture definitely play a critical role. Lack of communication, unreasonable deadlines, and unclear expectations will turn into burnout real quick. However, the power to create something from nothing can be really rewarding.
If you are interested and engaged with what you are working on, then you'll probably be happy. This isn't always the case though, since maintaining old legacy code is usually something all devs deal with at some point in their career. For me, I enjoy starting fresh and using the latest and greatest stack, but dealing with old and outdated technical debt always rears its ugly head.