A few weeks ago, I experienced the silent productivity killer every developer knows too well.

I started my morning trying to fix a backend bug. About 30 minutes in I get pulled into a quick meeting. After that, a production issue had popped up. Then my Teams get lit up with notifications. After that I switched to a different project. Then I had to review a pull request.  Then I had to attend more meetings. Then jump back to my original issue.

By the end of my work day I was exhausted.

And I had nothing meaningful to show for it.

I realized that day, I wasn’t overworked. I was context switching myself into cognitive bankruptcy.

The Myth of “Being Busy”

On paper, I was productive:

• Answered messages
• Attended meetings
• Reviewed Pull Requests
• Touched multiple parts of the codebase
• Fixed a bunch of “small” issues

But none of those required deep thinking.

The feature I needed to work on?
Barely moved.

Software development isn’t just about writing code. It’s about juggling many different ideas, solutions and problems in your head, at the same time:

• Architecture
• Business rules
• Side effects
• Database relationships
• Edge cases
• The assumptions you made 20 minutes ago

Every time you switch tasks, that mental model doesn’t just collapse.
It dismantles completely.

What Exactly Is Context Switching?

Context switching happens when you shift your mental focus from one task to another. In software development, that could mean anything from fixing a bug, to jumping in a meeting, quickly replying to a message on Teams, reviewing a Pull Request, switching codebases etc.

Every time you do this you force your brain to switch from one mental model to another.
That switching is expensive.

However the real damage of context switching isn’t the lost minutes. It’s mental fragmentation.

By mid-afternoon your brain feels foggy. Not because the work is difficult, but because your attention has been shattered.

You start:

• Forgetting small things
• Making avoidable mistakes
• Second-guessing decisions
• Feeling mentally fatigued

And then you tell yourself:

“Maybe I’m just not focused today”

When all along, the problem has been mental fragmentation.

Realisation

At some point I noticed something:

On days where I had 2-3 hours of uninterrupted work, I delivered more value in that time window than in an entire “busy” day.

Not because I worked harder.

Because I didn’t switch.

How Did I Reduce My Context Switching?

Nothing revolutionary. Just simple boundaries:

• Stay away from notifications during deep work
• Keep meetings grouped together
• Work on one meaningful task at a time
• Write notes or use helpful commit messages as a reminder of what you last worked on

Small changes.

Massive difference.

The Hard Truth

Most developers aren’t slow. They are overloaded with context switches. And the worst part? It’s invisible.

No Jira board shows “mental reload cost.”
No sprint review accounts for fragmented focus.

But your brain does.

Every single day.

Final Thoughts

We optimise code, queries, build times and deployments.

But maybe it’s time that we optimise focus.

Because in software development, our attention is one of the most expensive resources we have. And context switching is the tax we keep pretending doesn’t exist.