News for hackers. Stuff that matters.
Re:Common Mistakes of New Engineering Managers by sanderjd on Wednesday March 17, 2021 @09:45AM (#26491146)
What I would say is that it's possible but very rare to do this well, and furthermore that people often don't have an accurate sense of how well they're doing at it. The individuals on the team might know but might not want to say, but an even bigger problem is the individuals on the team not being aware there is a better way. I was about a decade into my career before I had an experienced dedicated engineering manager. I had already spent time as a tech lead / manager myself by then, and thought I had done ok, but experiencing a dedicated engineering manager made me see that I had actually done the job quite poorly.

You may be doing it extremely well! It does happen. But I can understand why you're getting skepticism.

Re:Common Mistakes of New Engineering Managers by camjohnson26 on Wednesday March 17, 2021 @12:05PM (#26493046)
A lot of us have been an engineer on a team where the dev manager thought they were contributing but were actually taking all the interesting architectural problems for themselves and making all the decisions, which quickly becomes extremely demotivating since the opportunities to advance your own skills quickly dry up and you’re left just mindlessly cranking out code. The worst is when an abstraction is imposed on the team that doesn’t adequately cover the problem, so you have to spend twice as much time bending the code to make the dev manager happy instead of doing it the way you think is best.

Granted this is just one way that situation can go, I’m sure there’s plenty of effective dev managers who still write code regularly, just hasn’t been my experience.