The 0.001x Engineer: Why Writing Less Code Creates More Impact
From musician to conductor—how the best engineers have stopped writing code and started orchestrating
Pause with me a moment. Bow your heads in silence for we are gathered here today to lay a dear friend to rest…
What can you say in a moment like this? This was someone…we all looked up to.
I even aspired to be like them at one point.
We used to talk about them in the halls their reputation grew across the org, from Engineering to Marketing and even up to the C-Suite.
When there was a problem…this was the person we could always call upon. And they never failed to come up with solutions and ideas we could try.
The 10x engineer built the platforms and systems that made this moment possible. This isn’t a rejection of that craft — it’s its next chapter
Yes…they were the best of us. Some would even say our Highest Performer. But…it’s time to move on.
The 10x engineer as we knew them has evolved into something different.
Say hello to the 0.001x engineer
That’s not a typo—0.001x, not 10x. They manually write less code but they create 1000x the impact. How?
Vibe Orchestrating! They’re no longer a musician playing in the band, they’re now the Conductor directing the Orchestra.
We spent decades hunting for developers who could write more code but we were measuring the wrong thing all along.
Getting Stuff Done
The 10x engineer mythology went like this: find someone who “gets stuff done”…writes more code, faster than others and ships 10x more features. Measure them by commits, PRs, velocity. Send the toughest gnarliest problems their way. Leave a case of Jolt and a pizza by the door, slide JIRA tickets under the door, knock loud and then walk away. Celebrate their output.
It worked because code was the bottleneck. Execution was scarce. Speed meant competitive advantage. More output meant more value.
I drank a lot of caffeine but I was never a 10x engineer, not even close, but I’m stubborn and I like problems and given enough time I could figure stuff out.
““In high-trust, high-automation environments…what would need to be true in order for you to ship code without reviewing the PR or looking at it?”.
Nowadays I have a CTO day job at a public company, I travel, I’m training for a race, my schedule is crazy, but I’ve built more stuff in the last six weeks then I have in the last six years. Well I didn’t build it…I “produced” it meaning I orchestrated it. I framed the problems, made the judgment calls, and let AI handle the mechanics. It’s a different kind of building.
We got it backwards. Speed is now less relevant and execution starts to become cheaper. We need to shift our focus upstream. The shift isn't about choosing between humans and AI. It's about engineers doing what we've always done when the tools change: we adapt, we learn, and we focus on the parts that still require human judgment.
Vibe Orchestrating
I started out vibe coding but nowadays, stealing tips from Boris Cherny I’m Vibe-Orchestrating — you heard it here first ;) .
By Vibe Orchestrating I mean that like Boris I’m not coding in an IDE anymore, I’m chatting with agents at the terminal, planning their work, answering questions and then updating Agent, Task and Role definitions.
Last time I talked about multi-agent configurations, but for most situations Claude Code or your favorite terminal based LLM interface, used correctly, is more than sufficient.
“Used correctly” matters a lot in that sentence.
I don’t mean adding an AI assistant to your existing human workflow. Let’s be honest: humans and computers are good at different things. Humans are creative and emotional. We have life events, relationships, shifting energy levels and more.
Speaking for myself — I’m inconsistent. My focus fluctuates. My performance varies depending on sleep, stress, or what else is happening in my life. I’m human.
We are not deterministic systems.
And to be clear, I’m not anti–human-in-the-loop. I’m advocating that we focus on what we’re actually exceptional at — framing problems, employing high judgement and expressing good taste — and let AI and agents handle the repeatable, process-heavy mechanics.
Adding an AI assistant to an unchanged workflow will help. But the real question is: can we reimagine the process from the ground up with AI as a first-class citizen and the human shifting left — toward intent, judgment, and strategic direction?
Engineering Roles don't shrink — they spread
Everyone’s concerned for their jobs and career paths, it’s a real concern. But I have good news. Let me tell you why engineering roles ultimately expand into the whole organization;
If it hasn’t happened already your entire C-Suite is trying to figure out how to use AI either in their Product or their Operations. Software teams are going to increasingly get pulled in to solve problems w/LLMs in places you never needed to think about software before. E.g. Alice from Legal or Bob from Accounting or Pat from Marketing.
Agents are infiltrating across the entire organization and the problems we need to solve are of a different nature.
This week (yesterday) I spoke with Harrison Chase, CEO and co-founder of Langchain. Sorry for name dropping but it was a privilege to speak with him and to hear his point of view first hand and the conversation w/Harrison highlighted some issues I’ve been thinking about for a while...
Soon we will see agents proliferate through all of corporate America. Enterprise IT groups are going to be plagued with new problems as a result. E.g. with teams collaborating on group-tasks involving multiple agents and sub agents how do you manage context? How do you avoid leakage of privileged information? How do you debug or replay a decision in a non-deterministic system so that you can improve your process over time? Do you need version control of enterprise level agent definitions? Do you need a way to delegate access tokens and credential management? How do you enforce Token limits? And Audit control. And so on…
What happens when your finance department is trying to close the quarter and their AI Agent runs out of tokens! These are real operational problems, and someone needs to own them.
How soon before the first court case where the defense is “It wasn’t me. It was the LLM?” And what does legal discovery look like in that scenario?
You’re gonna need to know which LLM instance, and which model type and what context caused what decision. Regulatory compliance, safety and security are nuanced and hard problems to solve. But the good news is there are smart people like Harrison already thinking about it.
And like as not they’ll all need Software support.
The bottom line is every part of your organization is going to need more engineering in the short term, not less. Over time, these skills won’t be confined to engineering teams alone — they’ll become part of how every function operates. I’m being dramatic to emphasize the point, but it’s hard to see how any organization doesn’t function without the support of engineering in the New World.
The Questions That Matter
Legendary music producer Rick Rubin famously stated he has "no technical ability" and knows "nothing about music" in terms of playing instruments or operating soundboards, admitting in a 60 Minutes interview that he brings "taste" rather than technical skill. He acts as a "reducer," focusing on stripping songs to their core, emotional essence.
As the world is shifting realtime what do we need to focus on? A 10x engineer assumes they are the driving force and so would ask:
How do I build this faster?
What’s the most elegant solution?
How do I enforce DRY principles but also make this perform? etc.
The 0.001x engineer is thinking far more abstract. They want to be OUT of the loop and instead asks:
Let’s make a plan, what are we actually trying to achieve? Let’s pressure test that plan (see Contrarian Agents).
Is this the right problem to solve?
How can I frame this to remove all ambiguity?
How might this initiative fail?
How do I make the agent self sufficient and if it makes a mistake how do I teach it for next time?
How do I improve the overall SDLC process for everyone?
The difference: 10x thinking optimizes for coding. 0.001x thinking optimizes for continuous improvement across the entire workflow.
For example…
Shifting Left (Preventing Waste)
The earlier you stop a bad idea, the bigger your impact.
The Engineer: Gets paged for a bug in production, fixes it. Impact: 1 bug fixed.
10x engineer: Spots the pattern, prevents 10 similar bugs. Impact: 10 bugs prevented.
0.001x engineer: Uses Agents to steel man the PRD and review the feature. The Contrarian agent pattern determines that the initiative is focused on the wrong metrics. That the primary success criteria of the initiative will move in correlation with the project but is not actually a causation metric. It reframes the entire project. Saves months of effort and time from lots of people.
Be like Rick!
How to Become 0.001x
The transition is uncomfortable. So far we assume the human is in the loop but this week I asked some team members… “what would need to be true in order for you to ship code without reviewing the PR or looking at it?”. What must be true: deterministic builds, automated rollback, reproducible context logs, token budget controls, versioned agent definitions, etc. The team is still thinking about that…
We’re closer than you think; Here are some concrete things you can start/stop this week…today!
Stop optimizing for commits — Your manager isn’t counting them. Impact doesn’t live in a PR or a diff. Does your human review really add what you think it adds?
Resist the instinct to code — I know that’s what you’re trained for but “How can I build this” is no longer the right question. “How can I orchestrate this so that it gets built whilst my team’s workflow improves” changes your impact from tactical to strategic whilst reducing your effort! That’s 0.001x!!!
Start questioning everything — If it’s repetitive, if it’s something you dread doing and takes your time, can you automate it? If not why not? Can you move upstream and automate that too?
Can you use background agents to pickup the busy work? Can you use an Agent or Skill to augment or improve the input into your process? e.g. JIRA Ticket enhancement or Figma design review?
Start sharing your discoveries with your team members and then literally start sharing Claude.md files or your LangGraph/LangChain/CrewAI role and task definitions.
Start connecting the dots through MCP — MCP is how your agents talk to your existing systems — Salesforce, Jira, Slack, whatever you’re already running. Don’t build it yourself, everyone has a connector now.
Any Final Words
Anyone can build anything. Wasn’t it Archimedes I think who said something like “with enough Tokens I can move the world”? The bottleneck has shifted. It’s not “can we build this fast enough?” anymore. It’s “should we build this at all?”
I wrote about what’s broken in how we build…Taste and High Judgment are the future. Read more here…
And so in closing….
We once again bow our heads and look upon the 10x developer…
Let us join hands and merge their final PR into mainline…
Let us close the final JIRA Ticket, and scale down their last K8s instance and release it back into the pool of eternal reserved instances.
Does anyone have anything they’d like to add?
Only this… Thank you 10x — your craft built the foundation we stand on. But now your watch has ended.
And until we meet again in that great Data center in the sky “go gcoinní Claude i mbos a láimhe thú” …may Claude hold you in the Palm of its Hand.
“Drop a note in the comments — what’s the biggest unlock you’ve found this year? How much time did it save? I want to hear your 0.001x moments.”
Francis here, thank you for reading and if you found this content helpful consider sharing with your team and let’s all support each other in this crazy moment in tech.
Ha, I literally used the same musician-to-conductor analogy in something I wrote recently. The bit I'd add is that the conductor still needs a well-structured orchestra. If the framework underneath doesn't enforce conventions, your AI agents play whatever they feel like and you're back to cleaning up after them. Explored this here: https://reading.sh/laravel-is-the-framework-for-the-agentic-era-76a8f8ec1fb4