Live data from Hacker News

Mental health in software engineering

vadimkravcenko.com

161–170 of 440 posts

Re: Mental health in software engineering

#161

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.

The industry is fundamentally about converting conscious thought into capital as efficiently as possible. So that it's bad for your mind makes sense to me.

Re: Mental health in software engineering

#162

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

One of the strongest skills as a business facing developer is being able to say no.

Re: Mental health in software engineering

#163
post #41

Earlier quoted context omitted.

In most companies I worked for the standard "I'm not feeling well today, taking a day off" was enough. Nobody asked for details.

one of the big companies recently replaced "sick leave" (only you can be sick to avail this, not a family member you care for) with "wellbeing leave" (you dont feel up to a day at work, take the day off - no questions asked) and doubled them from 5 days a year to 10 days a year. I am usually cynical about big corporates and their people policies, but this is one I can applaud.

In Europe, you don't generally get "sick days" - you're entitled to stay at home or in hospital for as long as it takes for you to get better (even for years, if necessary). In the meantime, your salary is paid by the state, so you're not an unproductive burden for your employer. At least that's how it works in Poland.

Re: Mental health in software engineering

#164
In the unforgiving realm of tech, where deadlines loom like tempests and demands soar higher than the tallest spires, a tale unfolds of a coder besieged by the storms of expectation. Leadership, with eyes set on horizons unseen, oft chart courses riddled with contradiction, whispering of features promised to titans, each deemed the pinnacle of priority. Yet, amidst the clamor for creation, a truth, stark and unyielding, emerges: to elevate two masters to the zenith is to court the abyss.

Thus, ensnared in this labyrinth of urgency, our protagonist wrestles with the specter of impossibility, urged ever onward by the mantra, "Make it so." A counsel of despair, for within the crucible of incessant toil, the spirit wanes and the flesh wearies.

In this odyssey of turmoil, the narrative delves deep into the quagmire of mental strife that ensnares those who toil in the shadow of unyielding expectation. It casts a light on the sanctity of boundaries, the paramount importance of safeguarding one's inner citadel, and the somber realization that, though we may strive with Herculean fervor, the fates of our endeavors lie beyond the realm of our dominion.

Herein lies a clarion call to the sentinels of the digital frontier: to honor the sanctity of mind and spirit, to question the altars of perpetual labor upon which we lay our offerings, and to seek a horizon where success is measured not by the quantity of our toil, but by the quality of our lives.

Re: Mental health in software engineering

#165

I used to be in (moderate) awe of young college drop-out CEOs. Then I worked for a couple of them. Now I refuse to work for startups that have 20-somethings at the top, because they really do not know how to manage or lead. They are motivated by fear of failure and having accomplished nothing so far they treat others like garbage. Avoid.

Data-driven ageism against old people --> OMG the industry is so ageist. Data-driven ageism against young people --> :crickets:

Re: Mental health in software engineering

#166
post #163

Earlier quoted context omitted.

one of the big companies recently replaced "sick leave" (only you can be sick to avail this, not a family member you care for) with "wellbeing leave" (you dont feel up to a day at work, take the day off - no questions asked) and doubled them from 5 days a year to 10 days a year. I am usually cynical about big corporates and their people policies, but this is one I can applaud.

In Europe, you don't generally get "sick days" - you're entitled to stay at home or in hospital for as long as it takes for you to get better (even for years, if necessary). In the meantime, your salary is paid by the state, so you're not an unproductive burden for your employer. At least that's how it works in Poland.

True, but that also means you cannot take a day off because you're not feeling it. You need at a doctor to attest that you're physically incapable of working. And in Germany, the employer has the right to demand a doctor's note from day one.

Re: Mental health in software engineering

#167

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

One of the strongest skills as a business facing developer is being able to say no.

Many people misunderstand this. Just saying 'no' and being firm won't make you successful, it's not a very useful. Saying 'no' while convincing others that 'no' is actually the best strategy is a great skill.

Re: Mental health in software engineering

#168

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.

You need wins to feel good. Or, projects with finish lines. But many projects go on year after year with no finish lines, ever, unless you or the company runs out of juice, or you move to a different company to do the same thing. In web dev, launch day is the closest you get, but it’s not a real finish line. Hitting kpi targets sort of counts, but it’s not psychologically satisfying like finishing a table or a piece of pottery or harvesting a crop and selling it or serving it for dinner.

Re: Mental health in software engineering

#169

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

This is why good developers are hard to find. There aren't a whole lot of developers who have the required technical abilities while also being able to communicate with clients/leadership effectively.

The CEO is doing that because they don't understand how things work in your org. If you're the one communicating with the CEO, then its your job to be persuasive when telling them why what they're asking can't happen the way they're envisioning.

If they come back with "make it happen" then you weren't persuasive enough.

Re: Mental health in software engineering

#170

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

> Adults will understand.

You're in a bit of a bubble. This is not the case for the majority of jobs.

Post reply on HN