# The maker's schedule is a shape

> Paul Graham named the maker's schedule. The 24-hour dial makes its fragmentation visible, so a protected block of focus reads as one unbroken wedge.

Published: 2026-05-27. Canonical: https://reassign.ai/blog/makers-schedule-drawn-round

Look at your day on the dial. The hours sweep round once, midnight at the top, noon at the bottom, and the work you've drawn sits on the ring as colour. Your day job is a blue band across the morning. The side project you fight to protect is a small teal wedge, late, after the kids are down. From here you can *see* whether tonight's hour survives, or whether it's been chewed into nothing.

In 2009, Paul Graham wrote about [the maker's schedule and the manager's schedule](https://www.paulgraham.com/makersschedule.html). Managers, he said, run their day in one-hour slots and switch between them cheaply. Makers (programmers, writers, anyone doing hard creative work) can't. They need half a day, unbroken, to hold a problem in their head long enough to solve it. And the two schedules collide.

*"A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in."*

Graham named the problem. He called it fragmentation. What he didn't have was a way to *see* it.

## A list hides the fracture

A to-do list can't show it. The side project is one line, the same height as "reply to Dana" and "book the dentist." A list tells you *what*, never *where*, so it can't tell you that the two hours you'd block for deep work have been split into two forty-minute slivers, each too small to think in.

A calendar strip hides it differently. It gives time a vertical axis, but it's still [a line you scroll](https://reassign.ai/blog/why-a-day-is-round): you see the morning, then the afternoon falls off the edge. A shattered afternoon and a clear one look almost the same on a strip: a tidy stack of boxes, top to bottom. The damage is real, and it's invisible.

That's the quiet trap of fragmentation. It does its worst work while looking orderly.

## The dial shows it

On the dial, the fracture has a shape. A protected maker's block reads as one continuous wedge of colour, a clean arc you can point at. A fractured one reads as a comb: little teeth of work with gaps notched between them, each gap a context switch you'll pay for. You don't compute the damage. You look at it.

And the negative space is lookable too. The open ring around your protected hour is the room you have left to bend the day into.

So bend it. A kid's recital lands at five. You grab the afternoon and slide it earlier, pull one block shorter, and watch the day rearrange itself *around* the teal wedge instead of through it.  The recital gets its place. The side project keeps its unbroken hour. Recurring events hold their ground; a fasting window frames the day without blocking it.

> A maker's block isn't a slot. It's a shape, and the whole day should bend around it, not break it in half.

## Or hand the defending to Claude

You don't have to draw the defence yourself. Reassign is also an [MCP server](https://reassign.ai/mcp), so you can [plan your day with Claude](https://reassign.ai/blog/planning-your-day-with-claude). Tell it the recital moved and ask it to replan the afternoon and protect ninety minutes for the side project tonight.

Claude looks first. It reads your real day, finds the honest openings, and proposes the shifts, using the same operations you'd reach for by hand. Then you watch each change land on the dial. Nothing magic, nothing hidden: the afternoon rotates, the teal wedge stays whole, and you approve it. You've handed off the fiddly part and kept the part that matters, which is seeing the shape.

Makers don't need a longer day. They need an unbroken one. And you can only protect a shape you can see.

## FAQ

### What is the maker's schedule?

Paul Graham's 2009 distinction: managers run their day in one-hour slots and switch cheaply, while makers (programmers, writers, anyone doing hard creative work) need half a day of unbroken time to hold a problem in their head. A single meeting can split a maker's afternoon into two pieces, each too small to do anything hard in.

### How do I protect deep work time in my schedule?

Give the block a shape you can see. On a 24-hour dial, a protected block reads as one continuous wedge and a fractured one reads as a comb of slivers, so you notice the damage before the day happens. When something lands on top, slide the rest of the day around the block instead of cutting it in half.

### Why do meetings ruin a whole afternoon of focused work?

Because the cost isn't the meeting's hour, it's the fragmentation. Splitting a two-hour stretch leaves two fragments too short for deep work, plus a context switch between them. On a list or calendar strip the afternoon still looks tidy; the fracture is real but invisible.

### Can AI help protect my maker time?

Yes. Reassign is an MCP server, so you can tell Claude the recital moved and ask it to replan the afternoon while keeping ninety minutes whole for the side project. It reads your real day, proposes the shifts, and you watch each change land on the dial before approving it.

---

More from Reassign, a 24-hour circular day planner: https://reassign.ai/llms.txt