2 ms·
Managing engineers is a new career, that is separate from being an Engineer. Many engineering skills don't transfer to management, even when you think they do.
by yoloswagins 9y ago
Managing engineers is a new career, that is separate from being an Engineer. Many engineering skills don't transfer to management, even when you think they do.
As a manager, one of the most important things you can do is schedule regular 1 on 1's with the people who report to you. Both "The Manager's Path"[1] and "Behind Closed Doors"[2] stresses this.
In about 4 months, it'll be helpful to review PG's essay, Maker's Schedule, Manager's Schedule[3]
Right now, you'll be coding most of your time, but you'll soon have more and more meetings. MSMS names the feeling of frustration around meetings, and describes how to handle so many meetings.
[1] https://www.amazon.com/Managers-Path-Leaders-Navigating-Growth/dp/1491973897 https://www.amazon.com/Managers-Path-Leaders-Navigating-Grow...
[2] https://www.amazon.com/Behind-Closed-Doors-Management-Programmers/dp/0976694026 https://www.amazon.com/Behind-Closed-Doors-Management-Progra...
[3] http://www.paulgraham.com/makersschedule.html http://www.paulgraham.com/makersschedule.html
- Eiriksmal 9y agoThanks for these. I've got Behind Closed Doors on order from a previous recommendation in this thread, but The Manager's Path appears to be especially apt! I've read the MSMS essay a few years ago, but had completely forgotten about it. The scheduling problem is actually something I've been struggling with the past few months in the run-up to this new role. When everything is urgent and you're the only one who can fulfill certain data requests, it's difficult to maintain progress on your own projects.