Leading a small engineering team without losing your hands-on edge
When I moved from senior engineer to running a team of five, the job changed in ways I did not fully expect. My calendar filled with other people's problems and the amount of code I shipped each week dropped sharply. This post is about the habits I have built since then to stay close enough to the work to make good architecture calls, while giving the team enough room to own their decisions and grow into harder problems.