I'm Jason Waldrip. For twenty years I've been moving from understanding what to build toward actually building it. On purpose.
I didn't start as an engineer. I started at the edge, in the room with customers, figuring out what they actually needed. Then I spent two decades moving closer to the thing itself: selling it, then specifying it, then managing it, then writing it, then owning the whole stack. Every step was deliberate: pair knowing what to build with the ability to actually build it. Most people pick one side. The interesting work lives where they meet.
Along the way I've been the founding CTO who took two apps from zero, the VP who collapsed a release cycle from weeks to hours, the engineer who rewrote the thing in the right language when the easy one was killing us. I've hired the teams, laid the infrastructure, and made the calls that either held or didn't. The receipts are on the works page.
what I actually believe
Judgment is the moat. 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. Agents go fast at both. That's the danger, and that's the job.
The train only moves as fast as its tracks. Cheap generation isn't an argument against a strong foundation. It's the biggest argument for one. A faster engine on bad rails derails sooner.
Teach a man to fish. The most durable thing a senior engineer ships is other engineers. Unblock, don't carry. Coach the principle, not the patch.
The needs of the many. I optimize for the biggest positive impact across the team, the product, and the users, not for comfort or ego. I'll make the hard call if it serves the greater good.
Move fast, build the tracks. Both are real. Knowing which kind of problem you're looking at (ship-it-and-learn versus slow-down-and-get-it-right) is the whole skill.
Time > capital. Treat people's time as worth more than money. And if you call someone an owner, mean it. Shared upside with fake or bad vesting isn't ownership, it's a story. Want everyone to act like an owner? Actually make them one.
None of that is theory. It's what twenty years of being the load-bearing wall taught me, including the lesson that being the load-bearing wall is itself a failure mode. The goal isn't to be indispensable. It's to build things that don't need you to stay standing.
// what I'm doing now
I work as a fractional CTO and CAIO, for founders drowning in AI-generated code and teams scaling past the leadership that got them here. The whole arc pointed here: not running someone else's engineering org, but bringing the judgment to whoever needs it. I do this through The Bushido Collective.
The Collective runs on a code, the eight virtues of bushido, rewritten for building software: honest assessments even when the truth is uncomfortable, respect for every call made before we showed up, the self-control to set ego aside and ship the right answer, and the loyalty to say no to work that's lucrative but misaligned. On the worker side, it runs on the belief above: real ownership, not the story of it.
work_with_me →A note on how this site was made: I write with Claude. I bring the experience, the frame, and the calls on what matters; the model does a lot of the drafting. I'd rather say that plainly than pretend the tool wasn't in the room, especially on a site about exactly this.