AI Coding Assistants Are Not Replacing Developers. They're Replacing Repetitive Work.
The replacement argument keeps missing what senior engineers are actually paid for. It is not typing. It is deciding.
6 min read
- Time on repetitive work
- 20%
- from 50-60%
- Time on architecture
- 40%
- from 15%
- Headcount impact
- Scope expands
- Feared
Every wave of tooling has come with the same prediction.
Compilers, frameworks, no-code, and now agents.
Each one removed a layer of manual work and none of them reduced the number of engineers.
What changed each time was what the job meant.
This wave removes the scaffolding. It does not remove the decisions.
§01 · The problem
Where the time actually goes.
- 01Boilerplate written from scratch every time
- 02Tests postponed because they are tedious
- 03PR descriptions written after the fact
- 04Documentation always out of date
- 05Repetitive refactors done by hand
- 06Onboarding to unfamiliar code takes days
Every item on this list requires an engineer's attention and none of it requires an engineer's judgement.
§02 · The mechanism
The AI workflow.
- 01
Scaffolding generated, not typed
Automation - 02
Tests written from signatures
AI Agent - 03
Docs and PR notes from the diff
Generative AI - 04
Engineer designs the architecture
Human - 05
Engineer makes the trade-off calls
Human - 06
Engineer owns what ships
Human sign-off
A person closes the loop: the workflow ends on a human or a check against a defined outcome.
- Automation
- Deterministic. No model involved
- AI Agent
- Model extracts, classifies, matches, or routes
- Generative AI
- Model drafts something a human will edit
- Human
- A judgement call only a person makes
- Human sign-off
- Final approval before anything ships
§03 · The difference
Before vs after.
| Before | After |
|---|---|
| Half the week on scaffolding and glue | Scaffolding generated in minutes |
| Tests written last, or never | Tests generated alongside the code |
| Docs treated as a separate chore | Docs produced from the actual change |
| Architecture squeezed into whatever is left | Architecture gets the time it deserves |
| Senior engineers doing junior work | Senior engineers doing senior work |
| Team velocity capped by typing speed | Velocity capped by decision quality |
§04 · The measure
Time saved.
| Task | Before | With AI | Comparison |
|---|---|---|---|
| Boilerplate | 2 hrs/feature | 5 min | |
| Test writing | Often skipped | Generated | |
| Documentation | 4 hrs/sprint | Automatic | |
| Time on architecture | 15% | 40% |
Continue reading
Tell us what you’re building.
Share a few details about what you need, and we’ll get back to you with a quotation.