Deep Work: Why the Pomodoro Technique is for Amateurs

The Pomodoro Technique is famous: Work 25 minutes. Break 5 minutes. It works wonderfully for answering emails, folding laundry, or writing invoices. It does not work for complex Software Engineering.

Why? Because writing code requires loading a massive "Context" into your brain.

• Variable states.
• Call stacks.
• Business logic.
• Database schemas.

It takes an engineer 15-20 minutes just to "warm up" and load this context. If your Pomodoro timer rings at Minute 25, it is interrupting you exactly when you were about to be productive.

Here is what we'll cover:

1. The "Maker's Schedule" vs. "Manager's Schedule".
2. Why "Flow State" is the only metric that matters.
3. A Productivity System that actually works for Coders (Time Blocking).

1. The Maker's Schedule

Paul Graham wrote the definitive essay on this.

• Managers live in 30-minute chunks. They change context constantly. A disruption is just another task.
• Makers (Coders, Designers, Writers) live in 4-hour chunks. We build large abstract systems in our heads.

A single 1-hour meeting at 2 PM doesn't just "take an hour." It destroys the entire afternoon. It fragments your 4-hour block into two 1.5-hour blocks—neither of which is long enough to enter Deep Work.

Mentor Tip: Guard your calendar. Decline meetings that don't have an agenda. Block out "Focus Time" publicly.

2. Flow State: The Holy Grail

Flow is that magical state where:

1. Time disappears.
2. The code flows effortlessly.
3. You hold the entire system architecture in your head at once.

Standard Pomodoro is an "Anti-Flow" device. It forces a context switch every 25 minutes. For developers, the goal is to sustain Flow for as long as possible (2-3 hours).

How to trigger Flow:

• Clear Goal: Know exactly what you are building.
• No Distractions: Phone in another room. Slack quit.
• High Challenge: The task must be hard enough to engage you, but not impossible.

3. A Better System: The "Deep Work" Block

Instead of 25-minute sprints, schedule Deep Work Blocks.

The Senior Engineer Schedule:

• 09:00 - 11:30: Deep Code.
  • Notifications: OFF.
  • Slack: CLOSED.
  • Goal: Ship the complex feature.
• 11:30 - 12:00: Admin / Comms.
  • Check Slack, Email, and PR Reviews. Unblock others.
• 13:00 - 17:00: Collaboration / Meetings.
  • Standups, Planning, Architecture reviews. Low-brainpower tasks.

4. Dealing with "Got a Sec?"

The most dangerous phrase in an open-plan office (or Slack) is "Got a sec?". It implies a small tax, but it carries a heavy penalty: Context Switching.

Strategy: Async Default.

• Don't answer instantly. It trains people to expect instant answers.
• Check batches: Check Slack once per hour (or during your Admin block).
• The "Headphones Rule": If my big headphones are on, do not disturb unless the building is on fire.

I once measured my interruptions. I was getting pinged every 11 minutes. I turned off all notifications. My output tripled in one week.

Summary

1. Context Switching is the enemy. Protect your RAM.
2. 25 Minutes is too short. Aim for 90-120 minute blocks.
3. Turn off notifications. You cannot code if your phone is buzzing.
4. Batch your comms. Be a Maker in the morning, a Manager in the afternoon.