BeCuriouzLearn something new every day
The engineer of 2026 doesn't write code — they write specs, design tools, and judge outputs
💡 Engineering is shifting from code production to specs, tool design, and judgment. The best engineers have taste and can articulate it as executable specifications.
The role of "software engineer" is undergoing its biggest transformation since the internet. 90% of developers now use at least one AI coding tool, up from 5% when GitHub Copilot launched in 2021. But the shift isn't just about writing code faster — it's about what engineers actually do.
The emerging consensus from Karpathy, Anthropic, and industry leaders: the engineer's job is shifting from code production to three higher-order activities:
1. Specification clarity — Writing precise specs that agents can execute. Ambiguous specs produce ambiguous code. The better your spec, the better the agent's output. Specs are becoming executable documents that agents reference directly.
2. Tool and interface design — Designing the APIs, MCP servers, and tool interfaces that agents use. This is where architectural decisions live. A well-designed tool eliminates entire categories of agent errors.
3. Judgment and evaluation — Reviewing agent output, catching subtle errors, making architectural tradeoffs, and building evaluation harnesses. "You can outsource thinking but not comprehension."
The engineers who thrive aren't the fastest coders — they're the ones with the best taste for what good software looks like, and the ability to articulate that taste as specs an agent can follow.