[CodeSgt]

It makes me sad that so many people seem incapable of understanding that you can both enjoy your job and be emotionally invested in the outcomes you produce while still living a healthy lifestyle.

It makes me sad that so many people here and elsewhere are content to just spend a third of their day 5 times a week for something they don't care about and don't get excited over. Is that really "healthier"?

I have a job where the code I write has a direct positive impact on the people the use our software. I enjoy seeing those positive outcomes. I enjoy seeing what my team and I created at the end of a hard sprint. There are certainly things I don't enjoy, as is the case with any job, but for the most part I feel good about how I spent those 8-9 hours at the end of the day.

[Test0129]

I think the GP is getting misinterpreted. The devil can be found in how you interpret "emotionally invested".

I try to stay emotionally detached from everything I do for a company. Even recently this helped me through a layoff and transition. I worked for a full year, mostly by my self, to put together a tool the company desperately needed to grow but couldn't afford a full team to build. Some 20,000+ lines of code lovingly put together to do the job exactly as described with full end to end tests and everything.

Then the new guys came in and said the project is scrapped. Stuff is getting shipped overseas, and they're going to instead try to kludge some off the shelf stuff into the role. All my work, a year and thousands of lines of code, gone in an instant. If I was emotionally attached to my work, in the literal sense, I would've been crushed. I wasn't because at the end of the day they paid me to make something that could be destroyed. In this sense, money is the most important thing. I wouldn't work for free even if I was promised what I was doing would save humanity.

I don't get excited by company visions or goals. I don't get excited when the CEO talks a big game, or the engineering VPs tell us how good we are. I don't care about hiring processes, meetings with the PMs, or the exact nature of whatever it is I am building. All I care about is the fundamental act of coding is enjoyable to me - and that's what keep me in the industry. I've been in the industry over a decade now. I realize sprint goals along with everything else a company focuses on is mostly trivia. The people in charge universally lack the ability to understand the nature and motivations of an actually talented engineer.

But it is eye opening that in over a decade I have never had a company say "we need to make this code easier to add to" or "we should make this as flexible as we could need for the future". There's never budget for good engineering. Just getting the product done. So it makes no sense to have any attachment to exactly what you do. But rather the art, so to speak, of doing it. Emotional attachment is how you end up in therapy after getting laid off. Save yourself the trouble.