Paul Graham, co-founder of Y Combinator, articulated a distinction that every engineer should internalize: there are two fundamentally different ways to structure a workday, and they are incompatible with each other.
The Manager's Schedule
- Unit of Time: 1 hour.
- Workflow: Command and control. Reviewing, deciding, unblocking. Changing tasks every hour is normal and expected.
- Impact of a Meeting: Minimal. A meeting is just another slot in the grid. The manager's job is meetings.
The Maker's Schedule
- Unit of Time: Half-day (4 hours minimum).
- Workflow: Building systems, writing code, designing architecture. Requires deep immersion and sustained concentration.
- Impact of a Meeting: Catastrophic. A meeting at 10:00 AM doesn't just consume one hour — it breaks the morning into two useless fragments. You can't start something hard at 8:30 AM knowing you have to stop at 10:00. And you can't get back into flow immediately after the meeting ends. The entire morning is effectively lost.
The "Swiss Cheese" Problem
When meetings are scattered randomly across a calendar, they punch holes in the day like Swiss cheese. Each hole is small, but the cumulative effect is that no block of time is large enough to do real work. A day with five 30-minute meetings spread across eight hours can produce less engineering output than a day with one 3-hour meeting block — because the latter at least leaves a contiguous afternoon.
The Lesson: If you are an engineer (Maker), you must ruthlessly protect your calendar from fragmentation. This is not selfishness — it is professional responsibility. Your organization hired you to build things, and you cannot build things in 45-minute fragments.