Maker's Schedule, Manager's Schedule
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
Paul Graham's 2009 essay separates two ways of using time: the manager's schedule, split into hour slots, and the maker's schedule, which needs half-day blocks for programming or writing. His argument is that one meeting can break an afternoon in two and discourage ambitious work earlier in the day. His remedies are office hours clustered at day's end and split days. The claims rest on his own experience and observation, with no data. For founders and engineering leads, it is a case for batching meetings.