Views·

An A–Z of software engineer wellbeing: A to C

AI anxiety, burnout and context switching. The first three letters of an A–Z on what this job does to the people doing it.

I've worked in software engineering for more than 25 years.

In that time I've seen plenty of what this job does to the people doing it. Very little of it ever comes up in a sprint review.

So I'm writing it down. An A–Z of software engineer wellbeing, a few letters a week.

A is for AI anxiety

Like most software engineers, I now use AI coding tools every day.

Whatever your choice, whether it's Cursor, Claude Code or Codex, the reality is that software engineering has changed for good.

With AI given as the reason for round after round of tech layoffs, software engineers are right to be worried about their future. They have to use, and keep up with, a technology that might one day replace them.

Despite all the reassurances that software engineers will always be needed, that anxiety is only natural.

It is something engineering managers and directors need to be aware of, and talk about openly with their teams.

B is for Burnout

A sprint is meant to be a short burst of effort.

After 25 years in software, I've seen what happens when you run two-week sprints back to back for years. The burst never ends.

You finish one and the next is already planned. There is never a point where you get to stop and recover.

Does that sound familiar?

C is for Context switching

For most of my career, context switching meant a meeting or a message pulling me off a problem.

Now I can have three or four coding agents running at once, each one stopping to wait for me.

The agents just run. I'm the one doing the switching.

If you work this way too, you'll know how mentally tiring it is by the end of the day.

First posted on Substack, one letter at a time, between 21 and 27 October 2026.

More in ViewsAll articles