Why the Past is Not the Future

The assumptions we built engineering teams on no longer hold. Here's what shifted — and what it means.

Four assumptions that
no longer hold.

01
Good designs require great designers
LLMs generate production UIs from a sentence.
02
Consuming APIs requires a developer
Anyone can integrate systems with natural language.
03
Small changes require an engineer
Domain experts ship directly.
04
Engineers are bottlenecked by typing speed
Engineers are bottlenecked by judgment.

If these assumptions no longer hold —
why should our teams and processes stay the same?

December 2025: Something Crossed Over

LLM coding agents hit a level of coherence that changed everything. Not gradually — in weeks. Engineers who adopted went from 80% manual to 80% agent-assisted coding almost overnight.

"LLM agent capabilities crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering... The intelligence part suddenly feels quite a bit ahead of all the rest of it — integrations, tools, knowledge, organizational workflows, processes."
Andrej Karpathy

The Process We're Still Running

Most teams are still running the old playbook. It made sense when the assumptions held. It doesn't anymore.

1
Product Owner
Talk to stakeholders, identify problems
1-2 weeks
2
PO + Designer
Work out solution, iterate with stakeholders
1-2 weeks
3
Product Owner
Write spec
2-5 days
4
Engineering
Technical spec, scope, estimate, prioritize
2-5 days
5
Backlog
Wait for prioritization
Days to months
6
Engineer
Implement
1-4 weeks
7
QA
Test and ship
2-5 days
Total
6 weeks to 6 months for a single feature

And the dirty secret? Most feature requests never make it through. They die in the backlog.

What's Possible Now

Small Changes

1
Domain Expert
Identify problem
5-15 min
2
Expert + LLM
Describe change, LLM implements
10-30 min
3
Expert
Review PR preview
5-15 min
4
Systems
Automated validation
5-10 min
5
Ship
Deploy to production
5 min
Total
30 minutes to 1 hour

Large Changes

1
Domain Expert
Identify problem
15-30 min
2
Expert + LLM
Design spec
30-60 min
3
Tech + LLM
Extend spec for system fit
30-60 min
4
Tech + LLM
Implement
1-3 hours
5
Auto + Tech
Review code + architecture
30-60 min
6
Ship
Deploy to production
5 min
Total
3-6 hours
Old Way
New Way
6 weeks to 6 months
30 minutes to 6 hours

This Isn't Theoretical

"I built Nexus — a production-ready system with authentication, semantic search, webhook integrations, comprehensive test coverage — in four days. Nearly 13,000 lines of code. While doing my day job as CTO."
Obie Fernandez

Leaders Who Stopped Coding Are Shipping Again

Person 2025 Commits Role
Tobi Lutke 800 CEO of Shopify ($100B+)
Jack Dorsey 757 Founder of Twitter & Block
"People I know are coding again, having mostly stopped as they moved into management. AI assistance means you can get something useful done in half an hour."
Simon Willison, co-creator of Django

The Process for This New Reality

The 12-Factor Process is the infrastructure playbook that makes this possible.

See the 12 Factors →