jason@im·a·cto ~ % whoami
REV A · JASON WALDRIP · FRACTIONAL CTO / CAIO · DENVER · taking engagements →
I am a CTO. I hold the map the agents can't.
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.
the_log
09:14
No-Code Is a Loan
You wired the flow on Friday and it worked. Eight months later a customer tells you it stopped, and the canvas has no diff, no test, no history you can read. No-code is a loan, and the interest comes due the day the glue turns load-bearing.
architecture08:38
Don't build the same app three times
A small team, and the plan is to staff three: an iOS engineer, an Android engineer, a web engineer. Three codebases, three release trains, the same login screen written three times and drifting apart by the second sprint. Or one React Native codebase that ships all three, one team, a bug fixed once. At GigSmart we took two apps from zero in eight months on exactly that bet. The tax is real: when a screen has to feel genuinely native, you drop down and build that piece native. So pay for polish where the product earns it, and bank the shared velocity everywhere else.
08:12
The Rewrite Looks Free Now
There's a file everyone on the team is scared of. Eight hundred lines, conditionals nobody remembers the reason for, a comment that just says don't touch this or checkout breaks. The fleet will rewrite it clean in a minute, and for the first time you can actually say yes, because the thing that always stopped you was the weeks of typing, and the typing is free now. That was never the real cost. The ugliness in that file is scar tissue, and the fleet regenerates the code without the scars.
judgment08:34
Your API is your agents' hands
Build the open API first, dogfood it, then invite others in. That used to be a pure growth bet: every team that integrates makes the product bigger than you could grow it alone. There's a second payoff now. The surface you built for outside developers is the same one your agent fleet drives. At Phoneware I put MCP servers over the platforms underneath so the fleet operates them like any other client. Design it once, for humans and agents both. Skip that and you're writing a second interface for the machines later.
08:30
Scale Is a Design, Not a Dial
You added instances and the system got slower. That's not a bug in the autoscaler. It's a ceiling that was drawn months earlier, on a whiteboard, by whoever decided where the state lives. Scale is a design decision made before a line is written, and no console reaches back to unmake it. In the agent era it's the most expensive decision of the invisible kind, because the bottleneck never shows up in the diff.
architecture08:34
Fourth of July weekend, and I was actually off. Phone in a drawer, kids outside, something on the grill. The fleet kept opening MRs, the merge train held the line, nobody paged me. I spent a lot of years being the load-bearing wall. Turns out the quiet reward for building the tracks right is that the thing stands up fine while you're not holding it up.