Hacker News new | ask | show | jobs
by wenc 854 days ago
Paul Graham wrote an article about the difference between a Maker’s schedule vs a Manager’s schedule. [1]

Powerful people are on a manager’s schedule.

Meetings are a unit of work for a manager, and they freely schedule meetings because there’s very little cost to them. The advantage of this schedule is you can have speculative meetings that potentially open up new opportunities.

This is very costly on a Maker’s schedule.

PG suggests partitioning the day to AM being maker’s schedule and PM being manager’s schedule. (A form of office hours).

This works if you have power and can swing this. But I’d be curious to hear what ICs do.

I personally just block off my calendar and decline meetings (with reasons given, always politely). I also entertain speculative meetings — I never want to shut myself off to new ideas. Most of my career has been built on serendipitous meetings by people who want to share a crazy idea.

[1] https://paulgraham.com/makersschedule.html

2 comments

Weirdly, being remote with a VERY geographically distributed team makes this easier. Meetings mostly need to fall into a fairly narrow range of time slots to be reasonable for everyone. That means almost all meetings land in a 2 hr time slot each day and the number than can be scheduled are limited so if it doesn't have to be a meeting, it isn't.
Or someone gets the short end, like me a European, who has to be on meetings with the US in the late afternoon. I do have the mornings free of meetings, so that's nice at least.
personally as a senior engineer & tech-lead in many past jobs I am very bothered by fragmentation of my time. I NEED a block of time to get serious work done especially if its not fully defined yet (i.e.. not like go code this function but more like add a service component). I have not yet read PG's blog on that but its something similar to what I track as in devtime-fragmentation-index. I wish there was a calendar plugin that tracks something like this as there is one to report total meeting time already.

Problem is its hard to convince managers that there was minimal work done this week because I did 3 hours of meetings each day but it was all spread out. its worse with non-technically sound managers because they need constant Q&A.

There was a time when I was working super late because of all the meetings and slack discussions in day time then to do actual coding work I had to find time later in night and my sleep schedule was getting messed up. this persisted until I introduced some hard boundaries. all in all I recommend blocking off time in schedule but thats not a scalable solution unless whole team agrees to it. plus dont get me started on different timezones working together.

> they need constant Q&A

Wants daily 20-30 minute stand-up/tag-up

Constantly bombards DMs since understanding is weak/research skills are poor

Pull engineers into fringe meetings "Just in case" (can't multi-task since full attention is needed to prevent any harm being done)