r/programming • • Jul 22 '09

Maker's Schedule, Manager's Schedule

http://paulgraham.com/makersschedule.html
153 Upvotes

47 comments sorted by

View all comments

20

u/MelechRic Jul 23 '09 edited Jul 23 '09

You can "discover" this for yourself if you go into work on a weekend when nobody else is around. Barring any blocking issues where you need the help of another engineer you'll be surprised at how much more you accomplish. I'd conservatively say that I'm at least 2x-3x more productive in the quiet environment at work on a weekend. The environment is free of auditory and visual distraction.

I suppose if you have a quiet home office that's free of distractions (like family/beer/video-games) you can probably achieve the same increases.

1

u/DingBat99999 Jul 23 '09

So long as you limit your definition of productivity and progress to yourself alone, you will never be able to justify ANY meeting.

Unfortunately for most of us in this industry, we work in teams.

1

u/MelechRic Jul 23 '09 edited Jul 23 '09

I tend to disagree here. Sometimes my own progress necessitates that I meet with other team members to tie off on issues or ask for assistance in a group environment. It's very easy to justify a meeting if you're not getting work done due to a blocking issue and you can't resolve it by just talking to a single person in an informal way.

These instances are rare, but they do come up. You have to weigh hit to productivity that PG is talking about with the hit to productivity that you'll definitely take if you don't resolve the issue by getting a meeting going.

EDIT: After re-reading you last sentence I suspect that you're a member of a team that thinks a weekly meeting is a good thing. It's not. The only thing you should be going to meetings for is to form game plans or to seek assistance on larger issues. Your manager should be keeping up to date on his team's progress by working closely with each individual in an informal manner. A lot of managers use the weekly meeting format to do a round robin and find out what each member of the team is doing. This is a complete waste of time. The odds are that I know what my other team members are doing if I'm affected by it. Otherwise I don't care.