A Weekend Build, and the Slow Years That Made It Possible
I built working software in a weekend. The speed is the least interesting part — it was borrowed entirely from the slow years before it.
Read →FOLLOW A THREAD
Lessons learned.
Decisions revisited, assumptions challenged, and judgment earned by doing the work.
Oldest first. Follow how the thinking developed.A weekend build, years in the making
Working software came together in a weekend. The judgment behind it came from years of deals, spreadsheets, and unfinished systems.
Read →Capture the work while it is still exact
Recording a decision in the moment preserves the reasoning that gets lost when the story is reconstructed later.
Read →Treat AI Like a New Hire, Not a Genie
A genie makes you careless. A new hire makes you a manager. Why everything I do with AI is propose-then-approve until trust is earned.
Read →Nobody Tells a Solo Operator They're Wrong
A solo operator loses the one thing that keeps judgment sharp: someone across the desk to say you're wrong. Here's how I rebuild that adversarial loop with AI — first a sparring partner you argue with, then a weekly coach that remembers what you committed to and holds you to it.
Read →Rebuilding the feedback loop
Working alone means losing the person across the desk who tells you you’re wrong. A sparring partner and a weekly accountability routine help rebuild that loop.
Read →