3 ms·
According to Junio Hamano he does 45% Communication, 50% Integration and 5% coding (Scratchin own itch) So 30% is rather high. A manager is not a coding posit
by lifeisstillgood 13y ago
According to Junio Hamano he does 45% Communication, 50% Integration and 5% coding (Scratchin own itch)
So 30% is rather high. A manager is not a coding position. If you are either you need to hire more people, or its not actually a manager role.
If you are not allowed to hire more people, its not a manager role. If you can, do so now.
- icedchai 13y ago30% is high, but 5% is still something. Integration is often highly technical and many would consider that "coding." On the opposite site, development managers who do no technical work quickly lose the respect of their team as being out of touch.
- ryanbrunner 13y agoYou're not really making a point, besides "a manager is not a coding position". This article is explaining why the author thinks it should be. It's not enough to say that managers shouldn't code, you need to demonstrate that either the authors points are wrong, or that there's a greater risk by spending 30% of your time coding. FWIW, I spend probably 30% of my time coding, I manage 13 developers, and I'm capable of hiring more people. If you're not good at pushing autonomy down on your team, you'll make yourself a bottleneck and have no time left to code. If you hire great people, and trust them to make the right decisions, a lot of traditional management overhead vanishes.
- lifeisstillgood 13y agoOk, that's fair. If I am going to give myself wriggle room, its that the vast majority of problems I have seen in poor software management have not come from a ex-Developer who has lost touch with the codebase, but from the other issues you / OP make - delegation, focus on team growth, structure and process improvement etc. If someone is self-diagnosing and saying "aha the reason this is all falling apart is because I am not coding more" its unlikely to be the correct answer.
- tlogan 13y agoWhen I was a manager in a big corp, 5% to 30% is spent code reading (basically understanding the machine). Many times together with the team / owner of the component. My job was not to do code review - we had a good process in place for that. It was always important to understand what is the internal state of the machine we are building/maintaining. So that I can answer to VP or PM team when they asks "we need to so X".
- nawitus 13y ago5% is 2 hours per week. That's a pretty short time to get one proper commit in.