There's a version of starting something where you gather everything you might ever need before you begin. Every tool. Every condition. Every contingency accounted for. And then, when it's all in place — when the moment is perfect — you start.
The moment never gets perfect.
A few weeks ago I published an episode about building an app on a ski lift. People liked the novelty of it. I was worried about that. Because novelty wasn't the point.
The point was: I gave myself a hard constraint — only my phone, only chairlift rides, done when I pressed start on the car — and something got built that wouldn't have gotten built otherwise. Not despite the constraint. Because of it.
I've been building
for longer than I want to admit. Started in Google AI Studio because it seemed like the right container. Made progress. Hit a wall I couldn't get past. Moved to VS Code. Made different progress. Hit different walls. Eventually landed in Claude Code, where things started to move. Really move.
And then I broke it. Two versions of the same codebase on two different computers, out of sync. I had something working and then I didn't. Most people would have stopped there. I almost did.
But I fixed it. Merged the codebases, preserved what mattered, came out the other side with one clean version. And what I learned in that process — about how code lives, how changes propagate, how you don't lose things if you know where to look — I couldn't have learned any other way. You can't tutorial your way to that knowledge. You have to break something real.
That's what constraints do. They make the experience real. They remove the option of waiting.
The 72-hour rule I use with clients is about this same thing. Authentic enthusiasm has a window. After 72 hours without momentum, the flywheel stops. Not because the idea was bad — because the space between insight and action filled up with planning, second-guessing, and the search for better conditions.
The founders I work with are brilliant. Creative. Full of ideas. And that's sometimes exactly the problem. When you've found the signal, the answer isn't more ingredients. It's fewer. Lock in. Go hard. Watch the data.
A beautiful recipe doesn't need everything in the pantry. It needs the right two or three things, cared for closely.
That's the whole argument.
I don't know if you like when I go philosophical like this. So I'm asking: does this land? Leave a comment on YouTube, reply to this email, send a carrier pigeon. I read everything.
If something in here is sitting with you — a constraint you've been avoiding, a project you've been waiting to start — take the Founder's Blind Spot Finder at https://tally.so/r/obeOlx. Good place to start.
This is Ground Control
Patrick
P.S. This week's episode is up — https://podcast.patrickrife.com/