Posts on Process.
5 posts tagged "Process".
The rebrand lived in the spec. The card read the README.
Two /work/ cards shipped in the same session. One named a product that had been renamed six months earlier. The other described the wrong project entirely. Both errors traced back to the same cause: the wrong document at the wrong time.
The roadmap was silently gone: four documentation layers and why none of them overlap
Six weeks after captainrandom's first devlog entry, a session to document the /learning/ work surfaced three problems. The most instructive: the roadmap had gone missing without raising an error anywhere. That is what four layers is for.
The video spec had a voice-clone bake-off. The same day, I cut generated voice entirely.
The one open decision in the video-pipeline spec was which synthetic voice would narrate: a clone of mine, or a premium API voice, picked by ear. I deleted the question instead of answering it.
The process changed. The docs didn’t. The fix was a folder.
Three times in the captainrandom repo, documentation drifted from actual practice. Each time the fix was the same: a dedicated folder with its own PRD, roadmap entry, and devlog trail — not a patch, but enclosure.
Audits find what's wrong, not what's missing
A page-by-page audit ran for three days catching deprecated ARIA roles, fabricated copy, and missing hover-pause behaviour. Then I opened the site on my phone and the nav menu wasn't there. Not wrong. Just not there. That's a class of bug audits can't catch, and the fix isn't to audit harder.