The interesting thing about the "test and build" kind of work that this "wolf" was working on is that this is team-oriented behavior that people in teams usuall

The interesting thing about the "test and build" kind of work that this "wolf" was working on is that this is team-oriented behavior that people in teams usually think the team won't let them do. It takes a kind of rugged individualism for somebody to buck the team to do this teamwork! On the other hand, my belief is that the main responsibility of engineering management is to be sure that stupid little details like build and test are taken care of. When they hear that "my build takes too long" or "I can't figure out how to write tests for X" they should take it as seriously as "I have cancer". If your "team" can't give a new programmer a checklist (or coaching) that gets them up and running quickly, it isn't really a team! Instead of this, most engineering managers are doing something else which might seem to have to value their managers but from my viewpoint of a developer is a complete waste of time. If instead of telling developers to suck it up about little annoyances they took responsibility for clearing them away they could 2x or 3x the whole team and not waste time chasing hypothetical 10x developers.