3 ms·
I agree, I'm troubled by the notion of not coding at all. However I think you need to separate "coding as part of the work effort to achieve tasks of the team"
by zmmmmm 8y ago
I agree, I'm troubled by the notion of not coding at all. However I think you need to separate "coding as part of the work effort to achieve tasks of the team" and "coding to keep you on top of the technical aspects of leadership". I actually think the latter is pretty essential, while it's a mistake if you are doing coding that is irreplaceable within the team. (I'm currently making that mistake, but that's another story).
- alistairSH 8y ago...you need to separate "coding as part of the work effort to achieve tasks of the team" and "coding to keep you on top of the technical aspects of leadership"... This. I've been in a management position for a few years now and was scrum master for a few before that. I try to grab a programming task every sprint, but I absolutely don't have the time to commit to large programming tasks that are critical to team goals. I'll grab some easy tasks (stuff that takes <2 hours or so). Or, I'll pick up some analysis/prototyping work that isn't time sensitive. Or, I'll just help team members when they struggle with complex problems. These days, I actually prefer mentoring or pair-programming with the junior developers. I have 4 of them on the team and making them more productive and independent is going to pay much larger dividends than trying to complete a complex task between meetings.