cefm said:
Code-monkeys make bad managers? It's more likely than you'd think.
I'm a "code monkey" (BS/MS Comp Sci) and I'm the head of software dev for a fairly large national company. I'm a great manager.
Brad's failings here have nothing to do with *his* myopic view. I know he's positioning himself as the sole arbiter of quality at Stardock, but frankly nothing could be further from the truth - there *are* other people who work at that company, on the same software, and spend just as much time with it as Brad does. The thing is - why did none of these people make a stink? Or if they did, why didn't it get actioned on?
This, in my opinion (and experience) is the key. If you want to put out quality software, you have to have an environment where people are encouraged to invest in the project and take ownership of their work and the entire project as a whole. That means, if you see something is not working, or stupid, *you say something*
As a boss, at that point, your only job is to listen.
My guess is, that the problem Brad has is an interpersonal one. Either he ignores the people he pays to do work on his behalf, or he has created an environment where they either can't or don't want to speak up. That has nothing to do with being a "code monkey", because you can see that in almost every business with any type of manager. It has everything to do with frankly, being a bit insecure.
