I lead a team of 7+ engineers and I still write code every day. People keep telling me one of those has to give. I think it works as long as I pick the right code: I give away the interesting problems and keep a hand in the boring ones.
Why I keep coding
In the weeks I stop coding, my technical opinions go stale in about ten days. I start reviewing PRs by pattern matching instead of understanding. I approve designs that look right and turn out to be painful, because I no longer feel where the codebase hurts.
Writing code is how I stay calibrated. The output matters less to me than what it does for my judgment.
Pick work that cannot be held hostage
I stopped taking critical path features. If my week explodes with people problems, a critical feature stalls with me, and the team waits on my calendar.
Instead I take the work nobody prioritizes: the flaky test, the slow query, the tooling. It's real code with real value, and no deadline depends on me finding a free afternoon.
The mistake I made early
Early on as a lead I did the opposite. I held onto the hardest problems because I was the fastest at them, and the team grew slower than it should have, because the problems that would have stretched them kept landing on my desk. That was hoarding the fun parts, and calling it leadership didn't change that.
It took me two years to learn to hand those problems over. The boring work turned out to be enough to keep my judgment honest.
Building something like this?
I'm Ahmed Mamdouh, a senior full-stack and AI engineer. I reply within one working day.
