![rw-book-cover](https://bs-uploads.toptal.io/blackfish-uploads/components/seo/content/og_image_file/og_image/908840/image_0-b362b5f0666404b391952d816c1709dd.png) ## Metadata - Author: [[karl-hughes|Karl Hughes]] - Full Title:: A Day in the Life of an Engineering Manager - Category:: #🗞️Articles - Document Tags:: [[My management principles values and practices|My Management Principles Values And Practices]] - URL:: https://www.toptal.com/engineering-management/a-day-in-life-engineering-manager - Finished date:: [[2023-03-27]] ## Highlights > I knew that I typically spent about one-third of my time helping my team solve technical problems or pairing with teammates. ([View Highlight](https://read.readwise.io/read/01gwfy911ancj5e5npg04cc68k)) > need to be good at helping their team members get “unstuck.” Sometimes this means answering technical questions, and sometimes it means resolving disputes between team members. ([View Highlight](https://read.readwise.io/read/01gwfyb4kfbg869bycvfxnp9dy)) > Technical work includes writing code, code reviews, hunting down bugs, pairing with teammates, and reading software updates and best practices. As my teams grew, the amount of time I devoted to writing and reviewing code dwindled, but I do think it’s important for engineering managers to spend at least [some of their time elbow-deep in the code](http://www.drdobbs.com/architecture-and-design/engineering-managers-should-code-30-of-t/240165174) ([View Highlight](https://read.readwise.io/read/01gwfyddd8esdxm5fq052jrq0h))