Mental health in tech
I’m not ashamed to admit the fact that I struggle with my mental health. Mental health issues are common among technology professionals. Perhaps this is even more common than in the general population, though I do not have any statistics to back this up. What I can say for certain, though, is that the technology world is not conducive to great mental health: we put incredible pressure on developers to deliver the impossible in unrealistic timelines, as well as to execute at a high level consistently when slow, careful thought is actually required.
I’ve seen a couple of posts on Mastodon lately that got me thinking about mental health. One advocates for a “slow tech” movement, claiming that destroying the mental health of technology workers for the last two decades has produced, in their words, a “mess.” I wholeheartedly embrace the concept of a “slow tech” movement, because I believe that developing software carefully, reducing defects, increasing testing, and producing quality are all important. But I think the issues are greater than just the speed at which we’re expected to work.
Technology professionals are often thought of as “cost centers” or expensive, rather than as drivers of productivity and profit margins. The recent layoffs are proof that developers and technology professionals are seen as expenses to be cut, not productivity boosters to be harnessed. Of course, interest rates and current economic conditions apply as well. But the fact of the matter is, many businesses see development efforts as expensive costs, even in sectors where the work they produceĀ is the product.
This constant push to “do more with less” and the threat of having your job evaporate overseas or out from under you creates a constant struggle with your self-esteem and sense of safety. And this in turn leads to mental health issues – feeling unsafe causes the “fight or flight” response to be overactive, and not respond properly when you faceĀ actual threats to your safety and well-being.
As an industry, we need a wholesale shift in the way we think about producers of software and technology. They are not costs to be cut or positions to automate away; they are artists and engineers and creatives that do an important task – even if we don’t fully understand it. We need leaders in corporations to understand that cutting teams hurts morale amongst those left behind, and doesn’t serve the greater goal of increasing productivity they way they expect. Not to mention the effects on the mental health – both for impacted workers and those who remain.
For me personally, while I have not faced a direct layoff, I know that the pressure to produce and perform is always there, and feeling like a cog in a wheel is damaging to my mental health. I work hard to manage this by having hobbies outside software, taking time to spend with friends and family, and stepping away from the computer when I don’t absolutely need to be working on it. This, plus therapy (everyone can benefit from therapy!) helps a great deal to reduce my anxiety and improve my overall self-image.
If you’re struggling with your mental health, you’re not alone. Reach out to someone – someone you trust – and let them know how you’re feeling. Seek a therapist to speak with about your concerns. If you’re in danger, call 988 (in the United States) or your local emergency number. Check out Open Sourcing Mental Illness. Remember that you matter to somebody, and they would be devastated if you weren’t here anymore. You are not your work – no matter how much work might define who you feel you are – and having things to do outside of the daily grind helps, too.