I'm gonna buck the trend here and say that this might be true.<p>Software development indeed has lower stakes than other professions (legal, medical). No one is going to die or be put in an iron cage for life as a result of our work -- well, at least not directly. But the bad consequences of their decisions leave with their clients. We are often tormented by our mistakes for years on end.<p>If you work in software long enough you also start to perceive a cyclical pattern in software "best practices" which leads to burnout. The hard problems you cut your teeth on as a journeyman become yesteryear's folly, and vice versa. If there are such a thing as fads in medicine or law, they certainly move at a slower pace than software.<p>It's also possible the developer makes <i>more</i> decisions, albeit at lower stakes, than doctors and lawyers. When you write a piece of code, you probably make dozens of tiny decisions per hour. Think about the last time you saw a doctor. Did you notice him/her pause at any point to think something over or make a decision?<p>So which is more prone to decision fatigue: a worker who makes a few decisions per day, based on a stable body of literature, that may lead to someone having a bad time somewhere far away in the world? Or a person who makes 100 decisions per day, based on fads, hunches, politics, and blog posts, that may increase their own workload by a factor of 10 in 6 months?
I have many friends in medical jobs where their decisions can have extreme effects on other people’s lives, to the point of risking life or death if they make the wrong decision for the patient or miss some key information.<p>From that perspective, software development feels like a low-stakes game.<p>Obviously there are many jobs with less decision fatigue, but I don’t think software development is uniquely bad compared to other highly paid professions like legal or medical.<p>All things considered, software engineering is one of the cushier high-paying careers out there. We definitely have it good.
No. Not even close. Most tech decisions are reversible (we even have term for it - technical debt), which lowers risk and means we don't need to avoid decisions. We have tools that mean we don't need to make repetitive decisions about a lot of things (linters, code formatters, codemods, etc) - once we've decided the tooling keeps everything nice and tidy so we don't have to question our decisions. We have it so much better than most people.
Comparing programming to tax preparation:<p>It depends, of course. Both have hard days where you are hyper focused and making critical decisions, and easy days where the work is fairly routine. I find tax prep to be more decision exhausting, perhaps because the tax code and IRS are involved, perhaps because the decisions need to be explained to the client.
Maybe. Personally I think the poor quality decisions are more likely to be the product of politics or some constraint that leads to not having a good choice and just having to go with the lesser evil.