Focus Routines for Programmers

Programming is one of the most context-switching-intensive knowledge jobs. Gloria Mark's research at UC Irvine found that after an interruption, it takes on average 23 minutes and 15 seconds to return to the original task. For a programmer holding a complex mental model of code, the cost is often higher: losing the model entirely and having to rebuild it from the code itself. A day with six interruptions can easily become a day of zero real progress. This guide gives you a concrete daily structure that defends against that.

The three types of programming work

• Deep work — designing, architecting, debugging hard problems, refactoring. Requires flow and cannot be interrupted.
• Shallow work — code reviews, emails, Slack, standups, small bug fixes. Can tolerate interruption.
• Learning — reading documentation, exploring new libraries, writing throwaway experiments. Best scheduled deliberately.

The mistake most engineers make is letting shallow work colonize the day, leaving only scraps for deep work. Flip it: protect deep work first, fit shallow work around it.

A realistic deep-work day

• First 90 minutes of the day: the most important deep block. Before email, before Slack, before standup. Your prefrontal cortex is freshest.
• Midday standup: compress to 10 minutes. Anything deeper belongs in a separate async thread.
• Second 90-minute block: the afternoon deep session. Often less productive than the morning — accept that and use it for continuation, not initiation.
• Shallow-hour batching: all code reviews, Slack replies and emails in a single 60–90 minute batch near end of day.
• Closing ritual: 10 minutes to write down exactly where you left off — "next: refactor the auth middleware, tests failing on edge case X." This is how you start tomorrow fast.

Defending flow

• Notification discipline. Slack on Do Not Disturb, email closed, phone out of sight during deep blocks. Not "silent" — closed.
• Calendar defense. Block your deep hours on your shared calendar as "Focus — do not book." Most people respect explicit blocks.
• The "parking lot." A physical notebook next to your keyboard. When an interrupting thought arrives ("must email X"), write it down and return to code. Writing offloads it from working memory.
• Pair programming strategically. It's deep work by design — two people on one problem with no escape hatch. Use it for the hardest problems.

Tools that help

The TimeSpeedy focus timer works well for 50/10 or 90/20 programming blocks. Set it at the start of each deep session and don't touch it until it chimes — the ring itself becomes a cue that interrupts are not allowed. For touch-typing-heavy work, warm up with a 30-second typing test to get into rhythm before the deep block begins.

The compounding effect

Two real 90-minute deep blocks per day produce more output than eight hours of interrupted work. Over a year, that difference compounds into architectural decisions, code quality and technical depth that visibly separates senior engineers from everyone else — not because they're smarter, but because they defended the time to think.