3 ms·
This is a fascinating thread to read. I would love to know when people comment if they also consider themselves a manager, or have managed in the past. The reas
by ChuckMcM 13y ago
This is a fascinating thread to read. I would love to know when people comment if they also consider themselves a manager, or have managed in the past. The reason is that I find management is a very different skill set than coding, and spending 30% on something that isn't making you a better manager would seem to be counter productive.
That said, I totally get the angst over managers who have never been coders. Sort of like Scully relating the sale of computers to being similar to selling 'colored water' (Pepsi vs Coke). Not so much in my experience.
There is also the question of scale, if you're a 20 person company I can easily see everyone writing code as well as doing other things, 50, 100, 2000 person company? Not so much.
And there is the question of perspective, a solid engineer is there to make the best thing they can, within the constraints of available CPU, memory, and storage resources. A solid manager is there to take a limited amount of money and time and ship the best thing their team can make within those constraints. So sometimes managers decide things one way, and engineers argue for a different way, it's always helpful to be able to see the problem from the other person's shoes. And yet my experience is that line managers, often drawn from the ranks of engineers, are more able to see the constraints the engineer is working under than the engineer is able to see the constraints the manager is working under.
I don't know if there is a 'right' way to blend those two roles. I suspect that if you're in a large company as a manager and spending a third of your time coding, you might want to check with your manager on how they perceive your performance. If you're in a small company and write no code you might want to check with your team to see if they feel they have it covered or not. But I can't imagine there being a 'blanket rule' like spend X% of your time coding that would have anything close to universal applicability.
- dasil003 13y agoTotally agree with everything you said here. The general response here is (understandably for HN) biased a bit too far in favor of coders. As a lifelong programmer who only reluctantly does management, I have to say that it sometimes seems just as hard for an engineer to understand what a good manager does as it is for a manager to understand what an engineer does. It's easy to make fun of a non-technical person because the terminology they don't understand is concrete but people management is every bit as difficult. Perhaps the problem is that it's relatively easy to weed out an incompetent programmer, but bad middle managers can often blend in or otherwise find ways to make themselves look good to upper management. In that sense a manager who codes is at least some kind of positive signal. But as a pure programmer I have to say this: two of the best managers I've had were not technical in any way shape or form. It's a mistake to think a good manager has to be technical in all cases. Good managers can add value in invisible ways dealing with the higher ups and shielding the team from politics and distraction. If the technical team is good and the manager has the appropriate level of trust then lack of specific technical knowledge need not always be a problem. As you say, it varies according to circumstance, but a lot of commenters here seem ignorant to the fact that there's more to the job than simply understanding the programmers world.
- pjmorris 13y agoIn the main, you say a lot of wise things. I have a couple of quibbles > spending 30% on something that isn't making you a better manager would seem to be counter productive. You're assuming coding doesn't make you a better manager... what if it does? >There is also the question of scale, if you're a 20 person company I can easily see everyone writing code as well as doing other things, 50, 100, 2000 person company? Not so much. Bill Gates shipped code up until 1989 [1]. Microsoft was between 3000 and 4000 employees at the time. Sure, he may be the exception that proves the rule, but maybe there's something to the notion that coding managers have a better sense of the technical market... of course, it depends on what market you are in. I've spent most of my time as a coder, but have managed from 1-12 people from time to time. [1] http://www.quora.com/When-did-Bill-Gates-last-write-code-for-products-that-shipped http://www.quora.com/When-did-Bill-Gates-last-write-code-for...
- ChuckMcM 13y agoIts a fair point, certainly understanding what the code is doing makes you a better manager. Sometimes that understanding is best done by coding up some things to test your understanding. I would be concerned though if, as the manager, your code was required to be complete prior to shipping the product. That would be a red flag for me.