Politics-Oriented Software Development

As an interesting counterpoint, one of the comments gives an excellent definition of a good software development manager: a bi-directional bullshit filter to keep the techs and suits from scaring each other (and in general being a single point of access to the development team for the rest of the company). Management at that level is very much an "if you've done it right, no one will know you've done anything at all" sort of thing. It's a subtle art but anyone who does it right is incredibly valuable.

I read this and started immediately reminiscing of past jobs. No classes in my engineering curriculum prepared me for this so I didn't "get it" when I first started out.

Did your schooling mention this sort of thing? If not, do you think they should?

I have been studying this level of software development since 1979 (sic, when I first encountered the obviously by then doomed MULTICS, saw how much had been dropped in the transition to UNIX, and wondered "why did it turn out this way?") and this is perhaps the single most useful document on it that I've ever read.

Plus a tremendous motivator to work in low politics startups, yes ^_^?

"Remember that managers are essentially secretaries who can fire you." ...I am precisely living through this right now. Of course not every manager is like that, but some definitely are.

If only someone told me of this article 5 years ago. Especially the part about working overtime ONLY if it's visible to everyone.

I really enjoyed reading this.

This is exactly why I went to work for a startup. We're becoming successful enough to start seeing some of this nonsense; when it gets too ridiculous, I think I'll be moving to another startup...