![rw-book-cover](https://miro.medium.com/max/1200/1*YeOjk5wvk_MKwhQZYlyaTw.jpeg) ## Metadata - Author: [[hasitha-pathiraja|Hasitha Pathiraja]] - Full Title:: Do Engineering Managers Need to Write Code? - Category:: #🗞️Articles - Document Tags:: [[My management principles values and practices|My Management Principles Values And Practices]] - URL:: https://medium.com/swlh/do-engineering-managers-need-to-write-code-d89903d68e8d - Finished date:: [[2023-03-27]] ## Highlights > As an engineering manager, you need to be able to gather context and understand the challenges your team is facing at a technical level. Doing this requires keeping your technical skills up to date. > A lot of managers use this as an excuse to continue contributing heavily to the codebase as a developer. > However, you can also accomplish this by, > • building tooling to make your team’s day-to-day work easier > • creating POCs to explore the feasibility of upcoming work > • cleaning up tech debt > • fixing bugs > • getting your coding fix outside of work ([View Highlight](https://read.readwise.io/read/01gwfzexkarmzzngpvzp90svpb)) > As I wrote about in [one of my previous posts](https://medium.com/@hpathiraja/building-trust-with-a-new-team-e4b2d9bb7d90), if you are a new manager who has joined an existing team, building trust and gathering context by coding alongside your team is very important. ([View Highlight](https://read.readwise.io/read/01gwfzgbwqw8pshxsea7m5rtfa))