The Wrong Panic
The Hacker News thread goes like this every week: "AI will replace all developers in 5 years." The reply: "AI can't even center a div." Both are wrong.
AI won't replace all developers. It will replace the developers whose work looks like an AI prompt. The ones who translate Jira tickets into code. The ones whose value is typing speed and syntax knowledge. The ones who are, essentially, human compilers.
Here's what AI coding tools are already doing in 2026:
- Writing boilerplate and CRUD operations faster than any human
- Completing functions from a comment description
- Debugging code by reading stack traces
- Generating tests from existing code
- Building entire features from natural language specs
If that list describes 80% of your workday, the Distance Test has bad news for you.
The Distance Test for Developers
The central question: "How far would someone travel to get what you provide?"
A developer who writes CRUD APIs? Distance score: near zero. Any AI tool — or any developer anywhere on Earth — can do that. The client wouldn't cross the street.
A developer who:
- Understands the business domain deeply enough to challenge bad requirements
- Architects systems that scale to problems nobody's solved before
- Debugs the gnarly, non-obvious, cross-system failures that AI can't pattern-match
- Mentors teams and translates between technical and business language
- Uses AI tools to ship 10x faster while maintaining judgment about what to build
That developer's distance score is high. Companies will pay premium rates and relocate teams to work with someone who has genuine system-level thinking and domain expertise.
Why the Lindy Test Gives You Hope
Software engineering is ~70 years old. That's young by Lindy standards. But look deeper: the core skill isn't "writing code." It's solving novel problems by breaking them into logical steps. That's thousands of years old — it's engineering, it's architecture, it's systems thinking.
The coding part is getting automated. The thinking part has survived every revolution since the abacus. The book shows you exactly how to shift your career weight from one to the other.
What the Book Gives You
- The Distance Test — score your dev role in 15 minutes and find your real vulnerability
- The Lindy Test — understand which skills in your stack are timeless vs. ephemeral
- Chapter 4's developer analysis — the most detailed of the nine career analyses
- The Centaur Model — become the developer who uses AI to 10x output while keeping judgment
- The Stack framework — AI handles execution; you handle architecture, domain knowledge, and decision-making
The Developer's Edge
Here's the irony: developers are actually in a better position than most knowledge workers. You understand the technology that's disrupting everyone else. The developers who thrive will be the ones who stop competing with AI at code generation and start competing at the things AI can't do: understanding messy human requirements, making architectural trade-offs with incomplete information, and building systems where the hard part isn't the code — it's knowing what to build.
That's the centaur model. AI is your exoskeleton, not your replacement. But only if you intentionally build toward it — starting now.