Re:How to fail as a new engineering manager
by bonniemuffin on Tuesday September 18, 2018 @08:18AM
(#18014556)
+1, I think it's critical to stay technically sharp, but that doesn't have to mean pushing user-facing code to production. I can only recall one time I've actually checked in production code since I transitioned to manager (and I definitely felt like I was shirking my manager duties by sinking a day into it), but I stay close to the code in 2 ways:
(1) I review the majority of the code that the team writes, and I also read other people's reviews to evaluate our code review practices.
(2) I hack around with new tools & technologies to evaluate them. This has resulted in some code bits in wikis documenting "here's how to get started with this thing", but not touching any prod systems. I usually save this kind of thing for our "personal projects"/hackday days at work.
Re:How to fail as a new engineering manager
by klenwell on Monday September 17, 2018 @11:17PM
(#18012213)
> Perhaps the best is to work with your developers code - write integration tests, evaluate checkins, research new tools.
Without really planning it, that's where I ended up. Also: establishing best practices and ceaselessly promoting them.
However I've seen a bunch of people hit middle-management then stop and its a really vulnerable place if you're looking for a new job. I think its really important to be able to keep some coding in new technologies as they become popular.
Perhaps the best is to work with your developers code - write integration tests, evaluate checkins, research new tools.