The Cost Nobody Accounts For
Every time you switch contexts — from deep coding to Slack, from a complex bug to a meeting, then back — you don't instantly resume at full capacity. Research suggests it takes around 20 minutes to return to the same depth of focus. If you get interrupted three times a morning, you may do zero hours of real deep work.
Most engineers underestimate this cost because the time appears on the calendar. You were at your desk. You were "working." But you were working at a fraction of your potential depth.
What Deep Work Actually Looks Like
Deep work is not just "no distractions." It's sustained, uninterrupted engagement with a cognitively demanding task for long enough that you can hold the whole problem in your head at once.
For coding, this means:
- You can trace the call stack without checking notes
- Edge cases surface naturally as you think through the logic
- You spot design problems before writing them
- You write significantly less code because you thought more clearly first
The difference in output quality between a 3-hour deep block and three scattered 1-hour sessions is not linear. It's qualitative.
How I Structure My Day
My rule is: no meetings, no Slack, no email before noon.
This isn't always possible, but I protect it as a default. Mornings are for building. Afternoons are for coordinating.
Specific tactics:
- Phone on Do Not Disturb until 12pm. This includes notifications from work apps.
- One task at a time. I write down what I'm working on before I start. If I get pulled away, I have something to return to.
- Explicit "available" windows. I check messages at fixed times (10am, 1pm, 4pm) rather than reactively.
The Hardest Part
The hardest part isn't the tactics. It's the social pressure to be immediately responsive. "Always available" is treated as professional virtue in most workplaces. Pushing back on this requires either seniority or explicit team agreement.
The teams I've seen do this best all have one thing in common: they've explicitly talked about communication norms, rather than letting them develop by default.
Start Small
If a full morning block feels unattainable, try 90 minutes. Calendar it like a meeting. Tell your team you'll be heads-down until then.
Do this for two weeks. Then measure your output. The numbers will make the argument for you better than any philosophy will.