Dillon Mulroy keeps the driver seat while using AI. The point is not to hand over the whole job. It is to keep enough shape and pressure on the work that the tool stays useful.
Notes
- 38:37 - Pi keeps the setup small. A short system prompt keeps the model on task. Related: Pi.
- 40:00 - Stable tools matter. A setup that does not shift all the time gives steadier results. Related: Dillon's skills repo, Dillon's dotfiles.
- 44:10 - Herdr gives him a place to juggle sessions and terminal tabs. It fits the rest of his setup because the shell stays close at hand and the work stays visible.
- 46:38 - Plannotator moves review out of chat and into a view that can be marked up. This is the best part of the talk to me, I think this is what I've been looking for! Links: Plannotator, LMV.
- 48:30 -
/treein Pi gives room to try a branch of work and come back without losing the main line. Related: Pi docs for sessions. - 54:18 - Types and interfaces come first, so the rest of the work has a clear shape.
- 57:00 - Before he trusts a change, he wants the command line to show that it works.
- 1:08:14 - Wayfinder looks like a fit for bigger work, where a clear path matters before the work starts. Related: Wayfinder.
Takeaway
This talk links well with the "design at the interface" idea from Should You Read the Code?. The shape of the work stays in human hands, while AI fills in the rest.