Live data from Hacker News

Mental health in software engineering

vadimkravcenko.com

151–160 of 440 posts

Re: Mental health in software engineering

#151

>You cannot take a sick day by telling your team, “I have mental issues and need a day off.” Yes, you can. You can say you need a mental health day. Adults will understand.

Maybe where you work but I just straight up tell them I'm not coming in. If I said this to my lead or boss they'd ask me why the hell I'm not coming in.

Re: Mental health in software engineering

#152
post #135

Earlier quoted context omitted.

I think it is a bit different depending on you country. I believe it is comparable in the us with the steep Healthcare prices. in Europe it usually makes sense to contract if you only have smaller projects.

Did both in few parts of Europe. Initially its normally better to contract (but you need to have some chops, nobody hires juniors on contract), but not all countries make this easy or even viable. Once you want to settle, if you want to settle, permanent job under normal circumstances offers better overall package. Maybe not outright amounts, but if you count in things like sickness, holidays, off for kids, social co…

yep, I am there myself. I seek to settle. as a part of that I also seek to transfer from having worked freelance for many years to take a regular job

Re: Mental health in software engineering

#153
I've come to believe that there's something about the practice of software development that causes, or can cause mental illness. I've seen a few colleagues over the decades have some very serious issues. It's really quite a serious problem in our industry, imho.

Re: Mental health in software engineering

#154

"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."…

And, as happened to me recently, the customer states in the demo that it's useless to them and let's just all move on to the next release.

Re: Mental health in software engineering

#156

Earlier quoted context omitted.

The phenomenon of showing up at Stanford and telling some 21-year-old that he's Jesus Christ and that you're going to give him millions of dollars is a wen on the American business culture matched only by corporate raiding. It's the nerd version of college football/basketball recruiting.

It's so weird. I started to think that maybe this is intentional. It looks as though investors want to invest only in over-optimistic people who believe that we're living in some kind of utopian paradise; at the same time they avoid investing in anyone who has had so much of a faint whiff of how the sausage gets made. It's like the entire system is desperate to keep optimists optimistic and pessimists pessimistic. Wh…

The VC investors don't need a startup that accurately predicts its odds, because most startups fail. So what they need are starry-eyed kids who have a distorted view of their chances of success, and in the small chance that they actually succeed beyond anyone else's wildest dreams (but within expectation of the distorted perspective -- which is the only way you can continue executing without being overwhelmed), the VC reaps the profits.

Re: Mental health in software engineering

#157

It's too triggering to do any more than skim the article, but having got the general gist of at least some of it, I shall write my top tip here in case it helps anyone (who manages to do it): Negotiate prohibitively high overtime rates.

Early in my career, I worked with a consultant who charged time and a half after hours, and double time after midnight. Every change we did was at like 10pm, and hardly any of them ever went well. I hope to one day find a way to do what he did.

This is what psychologists call "a boundary", and there's nothing secret about how it works: you just don't do the thing your abuser is asking you to do.

Re: Mental health in software engineering

#158
post #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…

Haha that was a great post because I was reading from the beginning thinking "gonna follow up tell this person they don't need to take abuse from sociopaths" then got to the end. Good job. Not every employer is a psycho but many are.

Re: Mental health in software engineering

#159
post #155

I haven't worked in a team or with a manager that wasn't receptive and empathetic to burnout or more serious mental health concerns. Guess I got lucky.

Could they actually do something about it?

What I found in my career is that the good managers do empathize and even sometimes try to improve the situation, but they simply can't.

More often than not the cause of the issues come from decisions done at the top levels of the company.

Re: Mental health in software engineering

#160

I've come to believe that there's something about the practice of software development that causes , or can cause mental illness. I've seen a few colleagues over the decades have some very serious issues. It's really quite a serious problem in our industry, imho.

I think Software Engineering attracts neurodivergent people. I am an adhd software engineer, and know a disproportionate amount of adhd software engineers.

I think that level of executive dysfunction and “catchup” is problematic

Post reply on HN