5 Ways to Be Hands-on as an Engineering Manager | by Sadhana Narendran | Jan, 2022

Now, I’m in a new role where the technology stack is completely new to me. However, I am keen to explore the technology landscape to understand opportunities and points of difficulty. I’ve found pair programming a good way to get to know the system better, while working slowly.

Photo by Michael Hoyt on Unsplash

Technical documents can take many shapes and forms. They can be “ready” files attached to code repositories to powerful microsites to full wikis consisting of code snippets, architectural diagrams, installation guides, and FAQ forums.

Automating some of your or your team’s routine tasks such as marking backlogs as outdated, improving the developer’s experience building or editing the pipeline or simply automating your tasks to give you some breathing time for hands-free, is a fun, low-effort, and effortless way. Weatherproof to keep your hands in the game.

Participate in technical design discussions that will often give you an overview of the different systems, services, layers, and transport protocol between them. If you spend some time in the system, you can ask intuitive questions geared towards often-forgotten areas like performance, security or data logging that can help guide teams to shift left on these requirements and build them early in the system. For you, this would be a great way to help the team while using your breadth of technical design expertise.

If you lead a team of more than 5 live reports, you will likely have less time than you would like to spend on coding features. Code reviews are great indicators of many things. They give you an idea of ​​the structure of the code, but also some subtle hints about the quality of the code being produced, the effort to keep technical debt in check, and the developer’s thought process.

Photo by Mohamed Rahmani on Unsplash

Leave a Comment