all frameworks
03 · Framework

SE 2.0 → SE 3.0

Code-first → Intent-first engineering
A
SE 2.0 · code-first
B
SE 3.0 · intent-first
Code
→ Main artifact →
Intent + spec
Engineer writes lines
→ Author →
Engineer writes prompts & specs
Code review + tests
→ Quality gate →
Evals + contracts + sampling
Copilot autocomplete
→ Speed lever →
Agentic workflows
Typing & reading code
→ Bottleneck →
Context, intent, evals
Algorithms & frameworks
→ Skill that wins →
Problem framing & taste

SE 2.0 — a world where the main artifact is code. Tests, reviews and CI all serve it. Copilots speed up such an engineer 1.5–2×.

SE 3.0 — a world where the main artifact is intent and a spec. Code becomes a derivative generated by agents. Quality is protected by evals, specs and contracts, not line-by-line review.

The map shows which practices, artifacts and metrics move with the transition — and what becomes the bottleneck when writing code stops being the hard part.

How to use this model
01

Name the primary work artifact: code, intent, spec, or eval.

02

Decide which quality gates should move from review to evals and contracts.

03

Find the new bottleneck once code generation is no longer the hard part.

Source talks
Share