Live data from Hacker News

Mental health in software engineering

vadimkravcenko.com

1–10 of 440 posts

Re: Mental health in software engineering

#5
"An example of uncertainty in business is when your CEO tells you they promised a feature to your biggest client and it needs to be built ASAP as highest priority, so all hands on deck. Then a day later they tell you another feature, completely contradictory to the first one, needs to be built as well and is also highest priority. When you tell them they both can't be highest priority, the answer is: make it happen."

At a certain point you have to just build a queue and start the next highest priority thing next. Too much WIP kills you.

Re: Mental health in software engineering

#7
>So, I will repeat it again: our greatest asset isn't the code we write. It’s us, alive, and living the life.

This is so important. Our work is an extension of us. Our state in the moment will bleed into all areas of life. There is nothing more important. As we are limitless potential. But only if we are living in the here and now.

Re: Mental health in software engineering

#8

"An example of uncertainty in business is when your CEO tells you they promised a feature to your biggest client and it needs to be built ASAP as highest priority, so all hands on deck. Then a day later they tell you another feature, completely contradictory to the first one, needs to be built as well and is also highest priority. When you tell them they both can't be highest priority, the answer is: make it happen."…

As a manager, if upstream changes priorities on me but what we’re working on is almost done, I just go ahead and finish it anyways.

When they eventually switch back to the original thing they are always surprised to know it’s been completed.

Re: Mental health in software engineering

#10
I'll dump this one here as it's still annoying me a bit. So one afternoon I'm sitting there and our sales guy John came in (you know who you are if you're reading this) and described what he'd managed to sell a client. I sat there and I scribbled on bits of paper for hours, did some research and went back to him with the point that it wasn't possible from an algorithmic perspective. Basically he'd assumed that if it worked for a couple of steps in Excel it'd be fine up to a few hundred. I scribbled out the mathematics a few times, wrote some prototype code and no the scalability characteristics approached "all the energy in the universe" levels of compute pretty quickly. O(wtf!).

So I go back to him and he accused me of lying and went and told the CEO. The CEO, a pretty chill guy with a doctorate, I was expecting to have a rational discussion about with but not he screamed at me too. I was downtrodden emotionally so I sheepishly said yeah I'll have another look and went back and started at it for another couple of days. No it was impossible. At that point I was stuck in a situation. I've got unemployment on one side and I've got getting screamed at inevitably. I just sat there in a depressed little hole with no options. I was angry, isolated and had no one sympathetic around. I suspect many people end up here.

Slept really badly that night. Woke up, got in the car and drove into the office. Got half way and got distracted by a cafe and decided I'd get breakfast and think some more about it. Sitting there eating a fat sausace, something just went ping, I SMS'ed John and the CEO with "fuck you I quit". I moved back in with my parents, did fuck all for 6 months, got another job, which was 80% less shit and the company I worked for went down the shitter about a year later because they couldn't deliver it.

If you feel like shit in a job, just leave. It's not worth it.

Post reply on HN