← all talks
↓ read the full manifesto
FEATURED TALK 16 SLIDES · 25 MIN
Vivecoding.
AI-assisted engineering as a campaign — not a roll of the dice.
I don't code alone — I'm the DM. The party: Engram (RAG memory), Gentle (grounding), Warlock (security), and the five SDD agents that turn the classical SDLC into something executable. This is what discipline + AI actually looks like.
Read the manifesto → Recording coming soon
Video being recorded.
The first delivery is happening live. Embed lands here when the recording is published. Subscribe to the RSS feed if you want a ping when it drops.
Vibecoding vs Vivecoding
Vibecoding
CHAOTIC NEUTRAL - Prompt the model. Ship whatever falls out.
- No specs. No design. Tests are optional.
- One model. For everything.
- "It compiles" = "it works".
- Tech debt grows faster than you can write it.
Vivecoding
LAWFUL GOOD - SDD pipeline: explore → spec → design → apply → verify.
- Multi-model cross-check. Right model, right job.
- TDD strict. Pure modules. Authz invariants.
- Code review baked into every PR.
- The AI amplifies the engineer — not the other way around.
If you remember nothing else.
Discipline beats vibes.
Specs, design, TDD, verify. The classical SDLC — just executable now.
Right model, right job.
Build a party. Each agent carries their class. Engram remembers, Warlock audits, Gentle grounds.
AI is an amplifier.
It doesn't replace the engineer. It makes a trained one 6× faster.
⚜ vibecoding is roleplay · vivecoding is a campaign with a DM ⚜