62 karma · joined February 20, 2021
If programmers can act with “complete entitlement” sometimes it’s only because they are some of the few workers who can demand something from their jobs, even without a union backing them. Most workers do not have that privilege/leverage.
Sometimes it’s better to say nothing.
Companies are very hierarchical so of course it makes sense for managers that most things should ideally come from one mind or a few agreeing minds. Then the average developer just have to do the grunt work.
So why is the book popular among developers? Because there is an elite cadre of developers in Brooks model which do have autonomy. I guess that cadre might also be known by other names.
[1] And the big man-month lesson of the book should be much more obvious now than it might have been back then: as you add more cooks you also have to take into account the communication overhead among all the new nodes.
Almost gave me a sinking feeling:
> If you behave that way you miss out on the part of the curve that we call “mastery.” That’s a state to the right on this curve, where there are still problems. Everything still sucks but it feels manageable.
> The grim paradox of this law of software is that you should probably be using the tool that you hate the most. You hate it because you know the most about it.