Building it yourself is the third thing I try
I built somebody else's idea into a working skill before nine and deleted it by ten. Not-invented-here is the accusation; here's the order I actually work in.
Tags
11 pages
Craft
I went looking for the reason not to build it
The requirements were done and I hadn't written a line of code. So I spent a day trying to talk myself out of the whole thing.
A Slack channel with nobody in it
I asked nine agent sessions to stop compiling for forty minutes. What came back read like a team of colleagues, and I haven't worked out what to do about that.
Which one needs me next
A dozen agent sessions running at once is not a capacity problem. Working out which of them is stuck is, and the obvious way to find out is the wrong one.
Ready for human
I run a coding session per repository and they can't talk to each other. For a while the thing carrying messages between them was me, and I kept getting it wrong.
What I took back off the shelf
I put my working practice on a public shelf, and then took some of it back off again. Working out which half was the interesting part.
They'll meet me eventually
Recording a voice clone in a wardrobe, what it sounds like when the accent slips, and the line I drew about where my synthetic voice may go.
A website for the place I still call home
Rebuilding the website for a fifteenth-century coaching inn, which happens to be my dad's pub and the place I grew up in.
The feature your users are already faking
The one real user of my photo tool was already faking a feature with a workaround. That workaround was the specification.
What burnout taught me (more than once)
Burned out more than once across twenty years, and the point is that none of them looked the same as the one before it.
