3 ms·
"Meetings suck." Preaching to the choir a bit? I'm not impressed. Nobody ever got fired for buying IBM|Microsoft|flavor du jour. No hacker every got shot down f
by korch 17y ago
"Meetings suck." Preaching to the choir a bit? I'm not impressed. Nobody ever got fired for buying IBM|Microsoft|flavor du jour. No hacker every got shot down for saying meetings suck.
- RiderOfGiraffes 17y ago> "Meetings suck." Is that really all you got from this? Did you actually read it? The thing I find about PG's essays isn't that his points are revelational, unexpected or intrinsically new, but that he so often manages to explain why these things are true, in such a way that I find myself nodding along with (nearly) every point. And he doesn't say "Meetings suck." He says: > Those of us on the maker's schedule ... know we > have to have some number of meetings. All we ask > from those on the manager's schedule is that they > understand the cost. And that's the difference between PG and so many others. He explicitly recognises that it's not a binary "Sucks" versus "Doesn't Suck". Meetings are essential, but costly. KNowing why they're costly is of enormous value. I'll be pointing my co-directors at this.
- mtanva 17y agoI think that there is a simple way to look at it too. If you're a manager, you're supposed to think & act with people as a priority. U're supposed to operate from 'Social Intelligence'. But if u're a programmer, u're supposed to operate from 'Technical Intelligence'. Since these two are very different and will result in different thinking & acting so the schedule will obviously be different.