Show Notes

“Have you got a sec?” is never a sec. In this episode we look at the real cost of context switching — not the interruption itself, but the fragile mental model it demolishes and the long, expensive rebuild afterwards.

We talk about why the problem isn’t the number of interruptions but their unpredictability, and how developers quietly adapt by pushing the hard thinking to early mornings, late nights and weekends — looking busy all day while the valuable work leaks into their own time.

We’re fair to managers, whose entire day is context switching, which is exactly why the cost is invisible to them. And we get into what actually helps: predictable focus time, genuine async, and rewarding the quiet work that looks like nothing while it’s happening.

Comments

Please leave a comment, positive, negative or just something weird.