Deep Work for Developers

Deep work for developers: ship the hard code.

The hard parts of programming do not yield to scattered minutes. They need long, quiet blocks where the whole system fits in your head. Here is how to protect that time and block what keeps stealing it.

Why deep work matters more for developers than most jobs

Writing code is not typing. The typing is the last five percent. The real work is holding a model of the system in your head: which function calls which, what state lives where, which edge case bites if you change this line. That model takes time to build and falls apart the second you look away.

This is what makes programming different from email or admin. You can answer email in the gaps between meetings. You cannot solve a race condition in the gaps. You need a runway long enough to take off, and most workdays never give you one.

What does a context switch actually cost a programmer?

A Slack ping looks like it costs ten seconds. It does not. The ping collapses the mental stack you spent fifteen minutes building. When you come back, you do not resume where you left off. You rebuild from a cold start, re-reading the code you already read, re-tracing the path you already traced.

Stack up six of those interruptions in an afternoon and you can lose the whole afternoon while feeling busy the entire time. The fix is not working faster. It is working without interruption so the stack stays warm.

• Warm-up cost: loading a complex system into working memory takes 10 to 20 minutes before you write a useful line.
• The collapse: one interruption can wipe that loaded state, forcing a cold restart.
• The real metric: uninterrupted blocks per day matter more than hours logged.
• The payoff: two protected 90-minute blocks beat a full day of fragmented time.

How long should your block be: 90/15 or 25/5?

Match the interval to the task. Not all coding is the same depth.

For a gnarly bug, a new feature on an unfamiliar service, or any architecture decision, run a 90/15 block. The 90 minutes give your model room to load and stay loaded. The 15-minute break is long enough to actually step away from the screen, which is when the answer to the bug often shows up.

For shallower work like code review, small ticket cleanup, responding to PR comments, or refactoring you already understand, 25/5 Pomodoros are fine. The work does not need a deep stack, so short rounds keep you moving and give natural checkpoints to commit.

GoFlow runs both. Pick 90/15 for the deep stuff, 25/5 for the review pile, or fixed mode when you have a hard stop before a standup. There is also an open stopwatch for the rare flow state you do not want to interrupt with a timer at all.

Block the rabbit holes before they open

Be honest about where you drift. It is rarely a useful place. You open a Stack Overflow tab to check one thing, and twenty minutes later you are reading an answer from 2014 about a problem you do not have. You alt-tab to Slack to send one message and read the whole channel. Hacker News is the worst, because it feels like work.

Willpower is a bad defense because the drift happens before you decide. The fix is to close the door in advance. GoFlow's free Focus Guard extension blocks the sites you choose the moment a work round starts, then opens them again on your break. You list Slack, Hacker News, Reddit, X, YouTube, and whatever else pulls you, once. After that the trap is just shut while you work.

One honest note: Focus Guard blocks desktop websites on Chrome, Edge, and Brave. It does not block phone apps. For the phone, the simplest answer is still the drawer in another room.

Track the task, not just the timer

A feature rarely closes in one session. You chip at it across days. GoFlow keeps each task on your list until you mark it done and adds up the total focus time you have spent on it. So a ticket you have touched four times shows you it has eaten six hours, which is useful when you estimate the next one. You see the work accumulate instead of guessing.

The distraction guard flags it when you switch tabs mid-round, so your deep-work hours reflect time you were actually heads down, not time the timer happened to be running while you read Twitter.

Protect maker time against meetings

Paul Graham split the day into the maker's schedule and the manager's schedule. A manager's day is a grid of half-hour slots. A maker needs the grid cleared. A single 3pm meeting does not cost 30 minutes. It poisons the whole afternoon, because you cannot start a 90-minute block at 1:30 knowing it will get cut.

So defend the morning. Put your hardest block first, before the day fills with pings and meetings. Batch your meetings into one part of the day and leave the other part as one unbroken runway. Tell your team the hours you are heads down. Most people respect "I ship between 9 and 11" once they know it is real.

A simple daily pattern that works

Start the day by picking the one hard thing. Open GoFlow, set 90/15, start a task named after the ticket, and turn on Focus Guard. Do one block before you open Slack at all. Take the real break. Run a second 90/15 if the morning allows. Save the afternoon, when your brain is foggier and the pings are louder, for code review and the shallow pile in 25/5 rounds. End with the wind-down so you can actually stop thinking about the bug.

Frequently asked questions

---

Keep reading