No True King
Recently I’ve revisited thoughts I’ve had about what it means to be a senior engineer. One summary I came across that I liked was making the move from “delivering” to “leading”.
And another I gleaned from an email Eric Raymond sent to Linus Torvalds regarding the latter’s over-reliance on his own genius. While not sent in the context of senior-level engineering, I think it’s still informative of an attitude adjustment that must be made when taking on the mantle of leadership:
The bill always comes due — the scale of the problems always increases to a point where your native talent alone doesn’t cut it any more. The smarter you are, the longer it takes to hit that crunch point — and the harder the adjustment when you finally do.
There will come a time when your raw talent is not enough. What happens then will depend on how much discipline about coding and release practices and fastidiousness about clean design you developed before you needed it, back when your talent was sufficient to let you get away without.
I would add “ability to delegate and elevate the work of those around you” to that last paragraph. It’s hyperbole to say that every line of code written by an engineering leader represents a failure, but I coach up-and-coming senior folks to think that way nonetheless.