4 ms·
Honestly, if there are that many battles in a developer's day, it's a sign of mismanagement. Some bad company leaders think that the right thing to do is consta
by gwbas1c 10y ago
Honestly, if there are that many battles in a developer's day, it's a sign of mismanagement. Some bad company leaders think that the right thing to do is constantly have people negotiate over silly details.
- jacquesm 10y ago> Honestly, if there are that many battles in a developer's day, it's a sign of mismanagement. Or a bad hire.
- dbcurtis 10y agoMaybe. The article outlines some behaviors that a good manager would immediately squash. Most people will conform themselves to the prevailing culture. When bad behavior is confronted honestly, squarely, and articulately by a manager, the offender usually conforms to the healthier cultural norms as articulated by the manager. Only if the bad behavior is confronted and still persists can you call it a truly bad hire. In which case it should be dealt with. No amount of productivity justifies being a jack-ass.
- arethuza 10y ago"He observed that a committee whose job was to approve the plans for a nuclear power plant spent the majority of its time on discussions about relatively minor but easy-to-grasp issues, such as what materials to use for the staff bike-shed, while neglecting the proposed design of the plant itself, which is far more important but also a far more difficult and complex task." https://en.wikipedia.org/wiki/Law_of_triviality https://en.wikipedia.org/wiki/Law_of_triviality
- shawn42 10y agoI think it's important to keep in mind that the OP is a consultant not a developer at a product company. I'm sure they end up working with external development teams that can't simply be dismissed (or fired), but must be worked with for the good of the customer. Simply saying "bad management" or "bad hire" takes too narrow a view on software development. The OP is a developer trying to get work done with the team, not a manager with authority over the others.