REV A · JASON WALDRIP · BUILDER · ENTREPRENEUR · TECHNOLOGIST · DENVER · taking engagements →
I've built and run engineering at consumer scale, first commit to the hard part, for founders drowning in AI-generated code and teams scaling past the leadership that got them here.
Volume is free now. Anyone can generate the code. The whole game is knowing which problem is move-fast and which one is load-bearing. That's the part I'm here for.
For eight years I was the most prolific engineer at a company I helped build. I'm now convinced that was a failure, not an achievement, and it taught me where engineering value actually lives.
AI is collapsing the cost of labor and execution. If we solve material scarcity, we don't end work; we liberate human potential to create at the top of Maslow's hierarchy.
The page a renter needs is on the internet they don't have yet. Solving that, and the twenty-odd jobs that run while nobody is watching, is what the word passive is actually made of.
There are two finished posts sitting in a queue on this site right now, waiting on me to read them. Nothing is broken and nobody is blocked, which is most of why it took me so long to look at it straight. I'd built a generator that never asks whether anyone downstream is reading, and that's the one topology I'd reject in a design review.
Three agents running, three diffs you'd each approve on their own, one red test suite that belongs to none of them. I spent longer than I'd like treating that as a prompting problem before I recognized it as the oldest problem I know how to solve.
You did the responsible thing and pinned the model string instead of pointing at latest, the way you pin everything else. That line in your config has a retirement date on it, and when the date arrives the requests stop returning anything. It's the first dependency I've shipped that expires on a schedule somebody else publishes.
I spent weeks rebuilding the website for the Starlink rental company I own. Then the orders started arriving as text messages, from people who never opened it. Ten weeks later there are five front doors and only one of them is a web page.
You're one commit from dropping a column, and the cheapest architecture review of your career is turning your chair around to ask the person behind you. Four seconds, no ticket, no record anywhere in your system. Nobody is behind you now, and a fleet won't turn around either.
The test went red, you handed it back to the fleet, and on the third attempt it went green. Nobody in the room can say what was actually wrong. That patch holds until the same bug picks a worse night, and then you're at 2am with no hypothesis and a fix you can't explain. At Brandfolder I walked into a product crashing on a memory leak. Finding it was the work. The change, once I knew, was small. Generation got cheap. Diagnosis didn't. Make the diagnosis the deliverable and let the fleet write the patch.