Re:Doing too much work on one's own before looping in others
by kelnos on Wednesday January 26, 2022 @02:06AM
(#30082665)
I prefer fairly non-technical engineering managers who stick to their lane. Their job should be to help manage the project schedule (in coordination with and guided by technical leads and product leadership), coordinate with other teams, coordinate with middle and upper management, and help their reports with whatever career development they need.
They should not be making technology decisions or specifying how the work gets done. They should trust their reports to not bullshit (and if that trust is broken, those reports should be fired). I think having a technical background can be helpful for these managers, but I don't think it's strictly necessary, and they should be doing essentially zero technical work as a part of their management job.
I've found managers who are like this to be incredibly useful and productive, and a pleasure to work with. Managers who want to get involved in technical decisions just get in the way and cause problems. Unfortunately a lot of newly-promoted former engineers can't let go of the technical work.
They should not be making technology decisions or specifying how the work gets done. They should trust their reports to not bullshit (and if that trust is broken, those reports should be fired). I think having a technical background can be helpful for these managers, but I don't think it's strictly necessary, and they should be doing essentially zero technical work as a part of their management job.
I've found managers who are like this to be incredibly useful and productive, and a pleasure to work with. Managers who want to get involved in technical decisions just get in the way and cause problems. Unfortunately a lot of newly-promoted former engineers can't let go of the technical work.