3 ms·
I think over the longer term, it's true, although not for individual hours. Knock some of pg's essays if you want (they deserve it), but "Maker's Schedule, Mana
by beat 12y ago
I think over the longer term, it's true, although not for individual hours. Knock some of pg's essays if you want (they deserve it), but "Maker's Schedule, Manager's Schedule" hits the nail on the head about productivity. http://www.paulgraham.com/makersschedule.html http://www.paulgraham.com/makersschedule.html
- Tyrannosaurs 12y agoI actually find this essay odd. What it says is fundamentally true but I'm curious about the allocation of "maker" and "manager". As someone who has worked as a manager and a developer, I value uninterupted time in both roles. It doesn't matter whether I'm planning, or writing a proposal, or coding - large chunks of uninterrupted time are good, a broken up day is bad and less unproductive. Certainly managers might more often have to respond to changing situations (though if you're a developer with any involvement in support you might question that) but if they opt to plan around frequent task changes when they don't have to that's just odd. To me it just feels like a difference between people who manage time well and those who don't, rather than a maker / manager distinction.