3 ms·
This article and much of the conversation here-in reminds me of THX 1138. There is a disconnect between how-to-manage and how-to-be-productive discussions on HN
by cyphunk 10y ago
This article and much of the conversation here-in reminds me of THX 1138. There is a disconnect between how-to-manage and how-to-be-productive discussions on HN. Definitely daily mails, and also probably weekly's with intense liability attached to them in the name of "quality" seem to go against promoting humane productivity.
Perhaps there are projects that require this level of management and communication, and perhaps there are people that work well with it. But there are also probably many projects that do not need such management overhead and where some types of people do not work very efficiently in. So, what I'm saying is that I think this management style shouldn't be an assumed default.
- clifanatic 10y agoMy experience is that this works well in an IT infrastructure sort of environment where you're assigned tickets that takes a couple of hours on the average. It sort of works in a project-based product development effort where programmers are implementing features and fixing bugs, but breaks down horribly on anything that involves any sort of research and experimentation (you know, the sorts of things that actually create breakthroughs and make money?) And God forbid you ever try to learn anything new: "Yesterday: read 50 pages of the ElasticSearch manual. Today: read 50 more pages of the ElasticSearch manual. Tomorrow: get fired for not having anything immediately profitable to put on status report."