Is it a necessity to maintain a hands-on approach with code or is it an overreach into the developer's territory? We delve into the roles and intricacies of an Engineering Manager, a Technical Project Manager, a Tech Lead, and a Staff Engineer, and how they all fit into the larger picture of a tech organization.
We delve into the why's and why not's — discussing topics like architectural decisions, hands-on coding, code reviews, the risk of micromanagement, and keeping a human approach amidst it all. We consider the impacts of being too technical or not technical enough, and how one can maintain their technical edge without losing sight of their managerial duties.
Further, we discuss the evolving skill sets in today's fast-paced tech landscape, the roles of MBAs and communication skills in the formation of an effective engineering manager, the pros and cons of reviewing PRs, and the delicate balance between coding and system design.
Finally, we talk about ways to stay technical as an Engineering Manager — from setting up local dev environments, routinely reviewing team PRs, participating in post-mortem reviews, and constantly challenging your team's decisions, and so much more.
