Early in my career I thought the best engineer in the room was whoever produced code the fastest. I chased that — typing speed, knowing every shortcut, churning out features. Then I started leading teams, and I got a clear view of who actually drove the most value. It was rarely the fastest coder. Often it was someone notably slower at the keyboard who somehow made everything around them better.
The story
We had two engineers I think about often. One was lightning fast — features flew out of him. The other was measured, almost slow; he asked a lot of questions and thought before he typed. On a stopwatch, it wasn't close.
But over a year, the "slower" engineer drove more impact, and it wasn't subtle. While the fast engineer was busy producing code — sometimes the wrong code, quickly — the slower one was asking the question that saved the team from building the wrong thing entirely. He'd notice the edge case that would've caused an outage. He'd write the design doc that got everyone aligned so three people didn't build conflicting things. He'd mentor a junior in a way that made the whole team faster. His individual output looked modest. His effect on the team's output was enormous.
That's when it clicked: coding speed measures one person's typing. Value measures impact on outcomes — and outcomes run through judgment, communication, and the people around you. The fastest coder optimizes their own line. The most valuable engineer optimizes the whole system.
What makes an engineer valuable
Judgment about what to build. Speed is worthless if you're building the wrong thing fast. Knowing what deserves to be built — and what doesn't — saves more time than any typing speed ever could.
Communication. The engineer who writes the clear design doc, explains the tradeoff simply, or aligns the team prevents enormous amounts of wasted work. Most expensive mistakes are communication failures, not coding failures.
Ownership. Valuable engineers see a problem through — the messy integration, the production issue, the thing nobody wants to own. They don't stop at "my part works."
Force multiplication. The best ones make everyone around them better — through mentoring, through reviews that teach, through raising the standard. One engineer who lifts a team of ten is worth more than one who's individually fast.
Coding speed scales one person. Judgment, communication, and mentoring scale the whole team. That's why the most valuable engineers are rarely the fastest ones.
Key lessons
Output ≠ impact. Lines of code is a vanity metric. Effect on outcomes is the real one.
The expensive mistakes are upstream. Building the wrong thing, miscommunication, missed edge cases — these cost far more than slow typing, and judgment prevents them.
Multipliers beat individuals. An engineer who makes ten people better outperforms a fast solo player, every time.
Speed without judgment is a liability. Producing the wrong thing quickly just means more to undo.
Action steps
If you want to be more valuable (not just faster):
- Slow down before you build. Ask whether this is the right thing at all. The best time saver is not building the wrong thing.
- Invest in communication. Write the design doc. Explain the tradeoff. Align the team. It feels slow; it prevents weeks of waste.
- Own outcomes, not tasks. See the problem through to "it actually works for users," not "my piece is done."
- Lift the people around you. Mentor, review to teach, raise the bar. Your value multiplies through them.
- Stop measuring yourself by velocity. Measure by impact: did the right thing ship, and did the team get better?
Final thoughts
I still admire fast engineers — speed is genuinely useful. But I've learned that the engineers who matter most are the ones with judgment about what to build, the communication to align people, the ownership to see things through, and the generosity to make everyone better. Those qualities don't show up on a typing test, which is exactly why they're undervalued and so worth developing.
If you're early and you feel slow compared to the fast coders around you, don't panic. Speed is the most overrated engineering skill. Build the ones that compound — and you'll out-impact the fast typists for the rest of your career.