A short closing from David — about five minutes — before you go.
What you actually have now
Five capabilities, practised rather than described:
| Studio | What you practised | What you keep |
|---|---|---|
| 1 — SEE | Separating the problem from the solution before you solve | Four Conversations Field Log |
| 2 — THINK | Staying in a conversation long enough for the design to change | Discovery Conversation Transcript |
| 3 — DESIGN | Reading design through what can be independently verified | Testability Review Card |
| 4 — BUILD | Keeping shared understanding alive while AI participates | Collaboration Protocol |
| 5 — REFLECT | Studying the traces of your own work | Personal Learning Loop |
The through-line
Nothing about good software engineering changed. Everything about how we practice it did.
Understand the problem before solving it. Design for change. Keep it simple and verifiable. Collaborate honestly. Keep learning. Those were true before AI and they are more true now — because AI amplifies whatever you bring to it.
That is why this was never a tooling course. Tools change. What you practised does not.
What to do on Monday
Not all five. Pick one — the micro-habit you chose in Studio 5. Use it on real work for two weeks, then look at what changed.
Small enough to keep is the only kind of practice that compounds.