Software team leads - is it normal to have no time to code. How do you cope with the lack of hands-on?

As title said, I'm wondering what is it like for you guys? I imagine in real life, it would be a more supervisory and mentoring position rather than the mythical 100x 1337 coder. For line-of-business softwares, alot of time is spent to gather requirements, clarify business rules, design and verify before writing first line of code.

For a team of SWEe, is the lead usually expected/better off handling all the clarification to clear the ways for team members? Looks like it synergies well with planning and work allocation. However, they are all time-consuming intellectual work, meaning I fear it leaves little room for actual development work after all the above. Context switching would kill any attempts to concentrate, I believe. If anyone has different accounts, please share and discuss. Genuinely interested in the position, need to understand the pros/cons versus staying as a humble SWE.

EDIT: got lots of insights, thanks. Keep them coming please.

UPDATE: would also want to hear about handling expectations. Those of you who were asked to both develop as much as the next SWE in the team while leading, how did you deal with that and what's the aftermath?

Posted Dec 4, 2016, 5:36 PM UTC · edited

5027
Loading comments…