Ask HN: Just made Director, now what? | https://news.ycombinator.com/item?id=14937290 (Aug 2017, only 38 comments) Book recommendations: >gtf21: Would recommend very highly: (1) Andrew Grove's "High Output Management" (controversial recommendation) https://amzn.com/dp/B015VACHOK/ $13.99 2015;4+stars;153 reviews >killjoywashere: I like Lazlo Bock's book, Work Rules! https://amzn.com/dp/B00MEMMVB8/ $16.99 2015;4+stars;…
Ask HN: Developers who became engineering managers, how was the experience?
71–75 of 75 posts
Re: Ask HN: Developers who became engineering managers, how was the experience?
#72I’m a senior technical staff member on my team. This means that I occasionally get to write code, spend lots of time debugging integration problems, and (as I see it) matching up people and problems that come in to the team. I don’t have direct reports, but I provide feedback to managers, am a team member, lead my own team, and lead / mentor team leaders of other teams. Delegation and Motivation are most difficult by…
Missing link (I assume) https://www.manager-tools.com/ :)
Re: Ask HN: Developers who became engineering managers, how was the experience?
#73Re: Ask HN: Developers who became engineering managers, how was the experience?
#74A programmer needs a lot of deep, focused work to do their job, whereas a manager needs to be available.
Managers are the spine and nervous system of a company. They need to transfer information from one part to another quickly. They need to communicate a lot, make decisions quickly. They train newbies, manage project progress, deal with issues.
A manager who wants to do technical work should probably limit himself to more shallow tasks like bug triaging or maybe setting up a checklist of things for the other programmers to do.