We had an employee that used this technique. Too often. When the company needed to lay off people to cut costs, their name got on the layoff list before anybody else's.
Businesses are not charities. They need to make money. And if an employee is not pulling their weight, sooner or later they will be let go. Using the law to extend your stay can only go so far.
Doctors, lawyers, teachers, and professional athletes all experience social reward and/or social contexts to their work. Software engineering is interfacing with an unthinking, unfeeling machine for many hours a day.
Furthermore, the whole point of the vast majority of software engineering is to sell loot boxes to kids to increase shareholder wealth for a pittance of the wealth created (or something not too different from that for at least 60% of companies). How many mainstream software companies are contributing to building a society that you yourself would like to live in?
To put it bluntly, many bad parents abandoned their kids to the internet where they found solace. Software engineering is a natural extension of spending too much time using the internet.
Poor mental health is a function of unmet needs... not feeling attractive, not feeling like you are contributing to the world or society at large, not getting laid, not feeling loved, not feeling worthy of love. All of these represent unmet needs, and I think software engineers struggle with these things more than a significant number of other professions because they are frequently intrinsic to why people become software engineers in the first place, machines don't care how socially inept you are, patients, clients, and judges do.
Software engineering is an incredibly people-focused career. You will need to be able to work with other devs, stakeholders, support, users.. everyone really. Going into a tech career thinking that it's somewhere you can avoid people is never going to work out well.
I enjoy working with people, actually. My current role is rapidly changing that.
Whereas in, say, government, people can just believe any stupid idea they want for an indefinite period of time.
As you can tell, I’m great with people. :)
Yes, you really can go into a tech career and avoid talking to people much, much more than other careers. Just stay out of management if you don't like talking to people.
They are not starved of engineers who "give enough fucks to speak up", they are starved of management who are invested and take enough responsibility to solicit direct feedback from the "assembly line" engineers and then make short term concessions on behalf of long term interests in defiance of what shareholders prefer.
Here is a quote from (imho) one of the top 5 greatest engineers of the 20th century, if not the number 1 greatest engineering leader:
> A major flaw in our system of government, and even in industry, is the latitude allowed to do less than is necessary. Too often officials are willing to accept and adapt to situations they know to be wrong. The tendency is to downplay problems instead of actively trying to correct them. Recognizing this, many subordinates give up, contain their views within themselves, and wait for others to take action. When this happens, the manager is deprived of the experience and ideas of subordinates who generally are more knowledgeable than he in their particular areas.
It's also worth reflecting on Pournelle's Law of Bureaucracy: https://www.jerrypournelle.com/reports/jerryp/iron.html
The only result of fighting the incentive structure put in place by management (far too often: punishment for pushed deadlines, reward for cutting corners) as an engineer is mental illness.
Here is Paul Graham using the word "nerd" and talking about the greater more complex idea: https://paulgraham.com/nerds.html
This is just your perspective and, IMO, it's pretty warped. Software engineering is not a low-status position, even compared to doctors and lawyers. You aren't lacking in status or not having sex because you're a software engineer getting paid $200k/year instead of a doctor paid $200k/year.
> Furthermore, the whole point of the vast majority of software engineering is to sell loot boxes to kids to increase shareholder wealth for a pittance of the wealth created (or something not too different from that for at least 60% of companies).
Lawyers have to defend clients they know are guilty to help rapists and murderers walk free, and file IP lawsuits for patents they know are bullshit so that their client can siphon off a settlement from a large company, just because it's cheaper than a court battle. Lawyers have been widely (and unfairly!) regarded as one of the most despised professions since Shakespeare.[0] Professional atheletes have long been subject of the media debate over being paid "too much" compared to the value they bring to society. Even if they were broadly perceived as providing negative value to society, which I don't believe, software developers would not be unique.
> To put it bluntly, many bad parents abandoned their kids to the internet where they found solace. Software engineering is a natural extension of spending too much time using the internet and becoming curious how it works.
This is becoming less and less true. Many junior devs who were born post-2000 that I talk to never had a computer growing up other than their phone, and their first real experience with PCs came in high school and university.
[0] https://en.wikipedia.org/wiki/Let%27s_kill_all_the_lawyers
I find that it definitely points to a time period when someone entered maybe not workforce, but the "IT world" let's say.
There was a time when programming in many places had definitely "unsexy" vibe among general population, with a lot of, well, painful "jokes", and all of that definitely set a "theme".
fast forward a decade or so to 2010 and suddenly IT is no longer that place where only losers go.
But the IT world is meaningfully different from software engineering. IT infrastructure (as distinct from creating software) pays less, generally, and is also regarded as much lower-status. IT is like auto mechanics to software engineering's automobile design. It's the blue collar equivalent, especially at the low level. At the high level, as far as I understand, it morphs with "cloud-engineering" or just general management and becomes higher-status.
Unfortunately, I think this comes from how the entrance into IT is gated by working on low-level ("have you tried turning it off and on again?") problems, and putting slightly awkward, new-to-the-workforce nerds in a position where they need to help a lot of people with their computer problems. Many of whom are (understandably!) frustrated that their computer systems aren't working and/or don't totally understand why they won't work. So IT gets to see people at their worst and most frustrated, and people get to see IT at its most awkward and least experienced. So hostility forms on both sides. And first impressions sometimes last very long.
Before that, some hugely successful people in software outside of "nerd" circles were discussed often in terms disconnected with tech and more as just other (if wildly successful, like Bill Gates) business people.
It’s not “you’re a loser”. It’s “you make a lot of money while ruining the world for everyone else.” Look at the jokes about Zuckerberg imitating a human.
He’s obviously one of the most powerful people in the world. But looked down upon by creating a socially harmful product. Like cigarette company or oil company CEOs.
Pay is not status. Software currently pays quite well, but in most companies today a developer is at the very bottom of the status curve. Developers are no longer allowed any say in what to build or how to build it, they are micromanaged by product managers and program managers and team managers and required to give daily status reports ("agile").
(I say "used to" because in the 90s developers were a high status role. You got to make all decisions and execute on them with great independence. Pay was much lower but respect was much higher.)
The other stress factor is that developers get decreasing respect every year they age. This is in contrast with basically every other professional role where experience is highly valued. Nobody wants the rookie heart surgeon, everyone wants the 60 year old who has done it thousands of times. But nobody wants a 60 year old software engineer.
I don't see how this is a bad thing, for a large and complicated product. For a small company where a team of 5 people can do the whole thing, sure, you don't need all this management, though I think some parts of the Agile methodology can be useful just for keeping people in sync. I worked in a small-ish team a while ago using an Agile methodology and it was fine: the program manager basically told us the feedback from the customer, and then it was up to us to decide what features to make to keep the customer happy and how to do it and how to schedule it. The Agile methodology just forced us to have regular meetings, and made it easy for the outside stakeholders to keep tabs on us and attend our meetings when necessary. Having daily habits in your life isn't a bad thing for many people, and that's basically what Agile was, in my experience: a way of having habits.
>Pay was much lower but respect was much higher.
No, it really wasn't. Maybe within the profession, but not to society at-large. Developers back then had little respect, until they started making lots of money in the dot-com boom, then people starting respecting the profession a bit more. Software development has never gotten the respect that doctors and lawyers get.
>Nobody wants the rookie heart surgeon, everyone wants the 60 year old who has done it thousands of times.
This might have some truth, but it's a bad view: generally, older surgeons prefer to use older surgical techniques that they learned decades ago, since they weren't trained on the newest techniques. The newer techniques generally are much less invasive and have faster recovery times. It's better to go with younger surgeons who have more modern training, but still some experience (i.e., not fresh out).
This is your own perspective, and again, it's extremely warped. If you think developers are at the very bottom of the status curve, go sign up to be your company's janitor, receptionist, HR/"talent acquisition", junior accountant, or any "operations"/"administration" role. Someone's gotta order and restock all the free beer and snacks in your office, you know.
And other than the janitor, those positions are all still likely 9-5 salaried positions that pay decently. Go be a retail worker, hotel staff, or waiter/waitress and enjoy being shit on by both your manager and your customers all day. Then come back and talk about how being a software dev is low status.
My sister is in medicine. Her entire day, down to each 30 minute block, is prescheduled for her. Often, she is forced to see multiple patients at once to increase revenues. The services that she is allowed to provide are governed by a completely separate insurance company. Strict metrics are tracked about the outcomes of each visit, including things like "how often did you see somebody for 35 minutes because that way you could charge for a full hour but spend less of your time."
This is far worse than anything I have ever experienced in software regarding tickets coming down from PMs or tracking of the amount of code committed in a week.
But then, I did not say that.
I said doctors get more respect as they gain experience, which is true.
This is what makes software developers a low status profession, i.e. many developers are glorified assembly line workers with little agency over their work (they do not make decisions).
Doctors and lawyers might have some form of management layer, but this is mostly a support function.
If you don’t think male doctors have more opportunities with women than male software engineers, other things being equal, I can’t take you seriously.
When you take a sick day, you're not supposed to say what's your issue.
The steps are the same. First they pile on more work on you, then gaslight you in believing your workload is the same as a junior employee and/or is subpar, then take you on a journey of “helping” you improve, document every small thing as a major flaw and then get you in that meeting with the HR.
Most places I've been at will suffer with known weak developers for a long time because a weak developer with domain knowledge is still more productive than many new developers without it and there's always the risk the new hire will turn out to be a dud as well.
A lot of the comments here seem to use the term mental health days without irony quotes. A mental health day is not a psychological crisis. It is a plea for a timeout from the workaday grind.
I was interviewing at a company recently and they called out that they offer 1 mental health day per month, in addition to other benefits.
Sorry but this is really naive. They won't come out and say it explicitly, because they can't, but many companies will just find a way to quietly replace you or hold you back in the organization if you are public about any mental issues.
I'm in an environment (military) were we actively work to prevent this. I have lots of kids (18-20yo) with mental health issues that are not helped by being allowed to take time off so casually. Our mental health experts want to keep people working because having them sit at home drinking/gaming does nothing. I have seen kids actually react well to increased "stress" on the job. Think basic training stuff. They are worked hard, go home tired and then actually sleep. Sending them home not tired leads to drinking and late-night gaming sessions after which they do not sleep and come to work the next day like zombies. Our people know how to spot this and adapt their schedules specifically to break the cycle. It wouldn't work for everyone, but we do need to accept that we are each not necessarily our own best therapists. If given more time off, many of us will simply amplify negative behaviors. The better answer is not I "need a day off" but rather "I'm booked to see the counselor at 08:00 tomorrow".
Are we talking US military here? I think I recognize the pattern you're talking about when you say:
> I have lots of kids (18-20yo) with mental health issues that are not helped by being allowed to take time off so casually. Our mental health experts want to keep people working because having them sit at home drinking/gaming does nothing. I have seen kids actually react well to increased "stress" on the job. Think basic training stuff. They are worked hard, go home tired and then actually sleep. Sending them home not tired leads to drinking and late-night gaming sessions after which they do not sleep and come to work the next day like zombies.
You aren't actively doing anything. You're saturating their day so that they're distracted from whatever underlying problems they face. They're too tired to deal with them so they sleep and repeat. I'd be curious to see your solution play out in the ten years post separation, but the VA may be ahead of you. For context (if you're not American) TAPS is what you take as you separate: https://benefits.va.gov/TRANSITION/docs/pstap-assessment.pdf (Section 4.C should have some relevant quotes).
I remember at some point a Navy Corpsman explaining to me that the goal of Navy medicine isn't to make you better, it's to keep you in fighting shape. Fighting shape doesn't need to be the best or most optimal shape, just enough to do the job the military needs you to do.
There were little activities to do on my base other than drink. I was paid very little, little enough not to afford a car. The cities I was stationed in were sounded by all kinds of loan sharks as a result. There were very few activities funded by the military that weren't somehow childlike or oriented for people with families. I was forced to live in a very old barracks that at times, frankly, barely functioned. While living in the barracks you can be summoned for duty at any time, unlike people who live off-base (married people). My life was as a Marine, so I'd be curious to hear an Airman's perspective. The services also tend to attract people who are actively attempting to leave home, so read from that what you will. None of these things are really unknown to the military or military leaders.
Would you let a troop take a sick day if they were any of those things?
I'd say I'm far from fully burnt out (we've all had our moments) but I think there is some career saturation point where people feel ownership over their free time and treat it with respect instead of "drinking/gaming".
Is wasting days off a symptom of youth? Is it because military employees lack autonomy? Is it just natural after years of selling your time to an employer?
Having served I agree that a military environment where your day is full and you're basically told what to do all the time, and you're maybe working extremely hard, can override some "bad thoughts". That said, it's not unheard of for soldiers to commit suicide, harm themselves or others, and generally suffer from stress related to the military environment.
I agree that simply taking a day off is not a fix and if you are worried about getting stuff done at work it might even make things worse. That said, being in a workplace where it's considered ok to take a day off if you need to, maybe go hiking or something, is probably something that alleviates stress from the employees.
Basic training is a nothing thing in the military. It does not represent what military life is like. It is just a temporary proving ground for new employees. That said, many units still do unit PT in the afternoons specifically so that people head home reasonably tired. Remember too that in the military, especially for young single people, "home" is wherever you rack out.
As to the GP's question:
> Has any company come out against mental health in the past 20 years?
Certainly not, but there are innumerable companies, software and otherwise, that while paying useless lipservice to the concept of taking care of employees, absolutely do not follow through. I have one friend who's simply unable to attend therapy because his insurance is shit and he's in too much debt to take on another. His employer has all kinds of things to say about how much they take care of their own, but he gets shit from his manager for taking "mental health days" so he doesn't, he just says he has the flu. Mind you he's no burger flipper, he's a seasoned sysadmin.
And, lest we forget that outside our IT professions, it's even worse. My wife is a cook and has bounced from one awful workplace to another many times, her treatment running the gamut from benign neglect to outright hostility at the notion of needing mental healthcare.
> I have one friend who's simply unable to attend therapy because his insurance is shit and he's in too much debt to take on another.
Most therapists offer sliding scale. Your friend should try that. > he gets shit from his manager for taking "mental health days" so he doesn't, he just says he has the flu
I do exactly the same, and I recommend it for others. There is still a lot of social stigma around mental health issues. Your boss doesn't need to know why you are sick. One thing I tell myself as I get older: "There is no Academy Award for the fewest number of sick days." It's OK to take a sick day every two months for your mental health.We are developing the device for that. May visit edenband.io to know more. And ask your peoples to join our waitlist to become our first users.
This sounds more like like papering over the underlying causes and likely exacerbating the problem; the fact that they're drinking heavily may be as an escape from the environment in which they are operating. I wouldn't call this active mental health prevention.
During undergrad, I had a lot of anxiety over my future career prospects, and I recognized that the best outlet for the excess "energy" was schoolwork that would keep my mind busy. So doubling down helped there.
On the other hand, my team at work just got done a month-long process that involved training another team from the ground up, while their supervisor was traveling for work, four of the five we were training were fresh out of undergrad and speedrunning every rookie mistake possible, and the fifth was a middle-aged man who thought he knew more than he did, and his constant rebuffing of our attempts to impart institutional knowledge made this process harder for everyone. Both of my immediate supervisors had to take a couple days off during this mess to decompress. Backing off was the correct response there.
Nobody ever actually came out and so, but I realize now that it was pretty common.
Our skillset becomes so uniquely tied to the company we work at that replacing a veteran engineer would take more than a year minimum. The differences between operations at two hospitals is probably minuscule compared to two tech companies.
It also feels like managers have received training in "burnout" so the few times I have uttered those words usually leads to some temporary white glove treatment.
Companies/managers have gotten alot smarter about this. The strategy is to hire enough and be managed to a degree such that the operation of any single system is never left leave to any single engineer.
So if your company is smart, yes you are replaceable.
It's a corollary of "the market can remain irrational longer then you can remain solvent".
In code the equivalent of this is having some bloated thing that's been touched by one too many shitty people who are only willing to learn just enough to mark their tickets done. That code turns into a ball and chain that no one wants to work on. Turnover becomes normalized
One of the reasons why most important stuff happens in open source
Certainly not for a single day!
I accept everyone's personal experiences with bad management, unreasonable timelines, and uninspiring projects, but those things are everywhere. Now add in patients and their families having the worst days of their lives in your presence day after day, high-pressure decision making, not getting even the chance to sit or go to the bathroom for nearly a whole shift. To top it off, if you have an "off day", that can earn you a lengthy investigation +/- a court case.
While it may sound insensitive, software engineering is nowhere near as complex or stressful as many (but not all) medical roles. It is both mentally and physically less taxing.
The attitude we should have is: yes, Mr. Successful Boss Man, you are a better human than me: you are more disciplined, don't have a problem with anxiety while dealing with a lot more stress, make more money and even look better. But these facts do absolutely nothing to change that I am crumbling and need a break. If you are so good at dealing with stress - write the software (or stitch up that patient) yourself, surely it would be easy for you, the superhuman?
But we won't do that. Instead we'll pretend we are 10x engineers or genius doctors until we either mess ourselves up, or make a big enough mistake. The realization needed to wake up is: the people pushing us to work harder need us. They actually couldn't have their successful business empire or their big fancy hospital without our work.
What makes me take it less seriously is framing it as a crisis in mental health. As much as people don't like comparisons the marketplace for our labor is inherently comparative, and people will optimize for the most money with the least hours/stress. I get that I'm providing anecdata but like I've said in previous comments, the stuff that software engineers I know complain about is from a much more privileged position than other occupations. Burnout is real, but if your version of burnout is someone else's idea of a mildly challenging day (which is my experience) it doesn't have the impact you want it to have. You may not realize it but there are roles in medicine where the work itself is inherently stressful regardless of how many concessions your employer provides.
If your goal is to argue that software engineers deserve higher compensation and better hours and more autonomy given the value they provide, it would garner more sympathy from someone like me. Proclaiming your suffering is at a boiling point feels like a lack of awareness.
> Software Engineers and Tech co-founders, like us, are more prone to hitting the lows.
I don't see where anyone was comparing software engineering/engineers to another profession. I certainly don't see where it was proclaimed a crisis.
I don't think it's productive to tell people others have it worse when they are promoting a discussion around mental health. I also don't think being well paid and having what appear to be great working conditions preclude you from having mental health issues.
This can be said so many times over regarding so many unproductive comparisons. Two wrongs, I've heard all my life, don't make a right. Nevertheless, people insist on dismissing wrongs that aren't, as it were, up to snuff.
Well, we as a society can both walk and chew bubblegum. If the OP isn't in here begging us for scarce resources, then he's wrong to interrupt our exchange of lived experiences.
I think stressors in the medical industry should be talked about. That seems important. And when they are, I won't be in the comments whining about software on-call.
The insane hours are actually counterproductive, but many people view them as a badge of honor. It's an odd metric to compete on (I can work more hours for the same pay!), and yet the competition is definitely there.
https://en.m.wikipedia.org/wiki/Libby_Zion_Law was enacted only after the daughter of a somewhat famous author died due to an egregious medical error made by severely sleep deprived residents. One has to wonder how many less famous people and their relatives have died prior to that, and what exactly is the benefit of having exhausted doctors running the show. And yet after the law was enacted many hospitals figured out workarounds to keep residents working insane hours (usually by requiring paperwork to be done after hours, unofficially), and many supported the insanity as a necessary rite of passage.
If you want to bring medical profession stressors to light, go right ahead. This is an article about a real phenomenon. Not every complaint must be universal or superordinate.
You don't sound "insensitive," you sound juvenile. If your profession is harmful to practitioners, perhaps attempt to cultivate solidarity instead of actively working to demolish it?
As someone who's familiar with artisanal cobalt mining in the DRC, I can attest that medical practitioners have it good, but I won't because that would be unconstructive in a conversation about the latter's working conditions. Grow up.
Remember anything you experience, there will always be some wanker trying to one up you or dismiss you
As much as I respect your personal experience, I think you make a mistake in assuming that it is universal. Further, you are also making the mistake of invalidating other people's individual experiences based on your perception of what the average worker does.
In other words, it is trivially easy to find software engineers who are burnt out to a much nicer crisp than the average doctor, and your dismissal of their suffering won't change a thing for them.
This isn't a contest to see which profession is most toxic to its workers. Our aim should be to find ways to prevent and mitigate these situations.
That said, I would argue that you underestimate the number of people in medicine who are burnt out. Many of my colleagues stay because it is a sunk cost financially/time-wise/reputatationally. You can pull up the numerous studies on burnout rates that have been done.
I'd anything it affirms my statement that you don't realize how much worse it could be. Like I said, there's a difference between taking down prod for 6 hours and getting sued for accusations that you killed a living being. This isn't intended to be a competition but it does become a bit absurd to watch people in the software world act like burnout from a micromanaging PM, unrealistic stakeholders, etc is the pinnacle of human suffering.
> On the whole I would rate the average software engineer as having a less stressful life than the average doctor
Those are very different statements, and I don't even disagree with the second.
Consider the possibility that the software engineers complaining the most about burnout are likely not experiencing the average amount of stress, so your casual dismissal of their suffering is really rather misplaced. Just as an example, a coworker of mine committed suicide, leaving behind his wife and two kids under ten. He didn't have it very very good.
I do entirely agree about software engineering being a lot less stressful though.
It's called "disagreeing". It doesn't "invalidate" anything.
I'm sorry but this is exactly what I meant by my original post. You don't realize that 4hr blocks in flow is an enviable luxury.
Granted my time was in a high acuity setting but let me cast it in more relatable terms.
Software 1 is brought to you with a complaint of the billing system dropping occasional transactions over the last 4 months. Now it is dropping 1 in 100 transactions. They use the Stripe API. It's your job in the next 15 minutes to debug and determine if there will be a complete service outage occurring within the next couple hours. If there will be an outage, you are expected to push a temporary fix to prod immediately and refer for continued review. If not, you must determine which parts of the billing system require referral for revision. Mind you that every decision you make can be reviewed years after the fact and can be litigated as they please.
Your assistsnt comes over with softwares 2 through 5 that were just submitted for your review. Software 2 has issues with a simple deadlock that could have been handled by someone other than you, but now it's your problem to deal with. Software 5 has been inexplicably ported from Delphi to Angular, and they've seen 2 others before you about why some of their native functionality broke, but now it's a big problem and they need you to look at it. There were some patches made by other devs but the stakeholders don't have access to them right now.
As you are looking into software 4,the assistant tells you "Dr zenzero, devops is on line 1 for you". They tell you that software 1 has more problems than described and it looks like it needs to be refactored in multiple areas. You update the PM that you can try your best to help but it's likely to still have a major service outage. 80/20 chance that the PM starts uncontrollably sobbing or starts getting upset at you that you aren't doing enough. Software 3 keeps complaining to your assistant that you're ignoring them.
So no, "Most doctors are not spending solid 4hr blocks in flow focusing on a highly complex problem" because they don't get that luxury.
I get to do that now and it's bliss.
If you live in a bubble of 16 year olds gifted new brand new cars and you complain openly how yours got dented, it's only fair that everyone else outside of that bubble rightfully calls you out and tells you to appreciate what you have.
> This hurt me to read on behalf of the OP.
Indeed. Taking time off for mental health reasons is no less legitimate than taking time off for physical health reasons.
I've never actually told any bosses that I'm taking a "mental health day" or anything, though. I just take a sick day, because that's what it is.
I am.
I worked alongside lawyers for almost a decade, providing them with non-engineering professional services. I also have a couple decades of experience in software engineering and startups.
The pressure in software engineering is something entirely different, and far worse, than what I experienced in the legal environment.
By and large lawyers are lawyers, not managers. Yes, there's a hierarchy of junior associate to senior-most partner but it's lawyers all the way up and down the chain. You don't have lawyers working under managers. And there's something about this that makes the pressures different. Pressures are there, hours are long, spouses are unhappy because the lawyers are always at work or distracted at home... but I never had anxiety attacks or mental health issues working in the legal environment whereas in the software and startup environments I did.
In legal, everyone knows the drill and you do the drill. And your superiors have done the drill.
In software, you often don't know drill. You just grind, often to satisfy someone who hasn't done the grind themselves. A company I once worked for – a successful public company – has constant openings for senior software engineers for this very reason.
For lawyers, it's a clear meritocracy based on how much you can bleed. For doctors, a kind of "virtue" in the work that cancels out some of the stress/BS. For software, it can be like temporarily joining the popular circus that's in town (similar to a lot of meme crypto companies)
I don't think it really matters what jobs are "harder". Nothing in the article is making the claim this is unique (or for that matter universal). The author's experience was in engineering management, and that's what they're writing about.
It's relevant to our industry insofar as it's reflective of an experience in the industry. I'm personally a bit cautious around claims of what is harder or easier because they tend to be pointless comparisons mostly used to dismiss valid criticism with whataboutism.
> I'm now 20 years into my career and never once have I come across this attitude. People take sick days all the time for mental health. I feel terribly for this person that they felt like they couldn't but this is far and away the exception rather than the rule.
I have definitely worked at organizations with a tech-bro startup culture where working non-stop (and drinking heavily) were idolized and anyone talking about mental health would have likely gotten a "man up"-esque speech (regardless of their gender, though shockingly these companies are mostly men). I have also worked at places where mental health was nominally respected but, like anything else, substantially more leeway was given to people perceived as high performers. I'm glad you haven't had to encounter anything like that, but I wouldn't even call it uncommon, nonetheless exceptional.
Who claimed it was?
Why does that even matter?
Whether you stepped in shit or are knee deep in shit, you're still in shit. Instead of having competitions about who is covered in more shit, why don't we help clean each other off? Stop comparing, we're not in a situation we need to triage. You are allowed to be sympathetic or empathetic to others, even if on average they have it better off than you. We're all humans. We benefit by coming together.
>Has any company come out against mental health in the past 20 years?
Where do you work?
> This hurt me to read on behalf of the OP.
> I'm now 20 years into my career and never once have I come across this attitude. People take sick days all the time for mental health. I feel terribly for this person that they felt like they couldn't but this is far and away the exception rather than the rule.
> Has any company come out against mental health in the past 20 years?
I'd say this is a cultural thing. For example, I have never heard of anyone taking a mental health day off. You just take vacation time and hope you come back normal.
Technically, you can take a sick day and the employer doesn't need a reason but if you work in an office environment, especially a small one, everyone knows everything. People know when you're sick and wonder if you're okay. They care and they ask.
My experience, your experience, Vadim's experience--interesting as anecdotes but none of it tells us anything about the "profession" without numbers.
So my intuition is that Vadim overstates the case as a whole, but it's still interesting as an anecdote because what I think he's feeling is pretty common and it's interesting enough to read what worked for him and what advice he has for someone who feels like that.
I do think that in reality it's rare for an engineering leader to take "mental health" days off but all of my engineering leaders have taken plenty of time off and encouraged others to do the same. I haven't worked at a death march cadence in probably almost a decade (and I quit that job pretty quickly when it started). I don't think your experience is homogeneously true, I think people are pretty reticent to take time off (it's why "unlimited PTO" even works in practice) and it's probably worth it to continue asking why.
All of these have their specific stressors, all of these professions have loads of articles about how people are leaving these professions due to how hard they are.
All of these jobs tend to lead to them consuming your free time if you don't set boundaries, all have deadlines that lead to stress.
>You cannot take a sick day by telling your team, “I have mental issues and need a day off.”
This hurt me to read on behalf of the OP.
I'm now 20 years into my career and never once have I come across this attitude. People take sick days all the time for mental health. I feel terribly for this person that they felt like they couldn't but this is far and away the exception rather than the rule.
Has any company come out against mental health in the past 20 years?