I've come to a realization that managers and programmers have something in common. The bad ones try to perpetuate job security by creating complexity (whether i

I've come to a realization that managers and programmers have something in common. The bad ones try to perpetuate job security by creating complexity (whether in code or interpersonal issues) that only they can navigate. The good ones want to do their jobs so well that they "program" (literally for engineers, figuratively for managers) themselves out of a job, so they can graduate to better things. You see this most strongly with consultants. The good engineer does the best work he can, assuming it will lead to more challenging and interesting projects in the future. He's not worried about job security, or at least not enough to do things that are unethical; he assumes that doing a good job and becoming better at his work is job security. The bad consultant obfuscates code, documents poorly, and tries to make it impossible to ever fire him. He's not trying to bigger, badder (and more lucrative) projects in the future; he's just aiming to keep whatever income stream he has in perpetuity. I think that managers exhibit the same dynamic, and I think that solving this problem requires recognizing it and watching for the warning signs early on. I'm strongly in favor of open allocation, but that's not quite the same thing as "no management", which I think might take the idea too far. Why? Because management is a fact of life; some people will have more power than others, and I'd rather it be dealt with in a fair and reasonable way than in an ad-hoc and unstable way. Having a permanent class of entitled (literally, not necessarily pejoratively) managers may not be the solution, and I support making people more self-managing-- actually, I'd use the term self-executive-- but acknowledging the basic fact of management, and encouraging the positive manifestations while avoiding the negative, is probably healthy as well.