Three months of commits. Private repo. Never deployed. That’s not a story about a bad project. The project was fine — a UAV mission planner that could generate flight paths and export KML files. Clean idea. Technically interesting. Real use case. It just never left the hard drive.
Here’s the thing nobody tells you about side projects that stall: the blocker is almost never the code. The code gets written. It gets rewritten. Refactored. The folder structure gets reorganized twice. A new branch appears called feature/cleanup. Another called experiment/maybe-better-approach. The repo grows. The project doesn’t.
You’re not stuck because you don’t know how to build it. You’re stuck because there’s no moment that requires it to exist.
The AI Illusion: Faster Planning, Slower Shipping?
A METR study published in July 2025 (arxiv.org/abs/2507.09089) found that experienced developers working with AI tools were 19% slower than those working without them on real-world software engineering tasks. That number gets cited a lot as an AI critique. I think it’s pointing at something different. It’s not that AI is useless. It’s that AI optimizes for the planning layer — the architecture, the boilerplate, the “how would you approach this” questions. It gives you a very good plan very fast. It does not give you the 13 days that follow the plan.
The Discipline Deficit: What AI Can’t Deliver
My first sprint user shipped in 13 days what had been sitting untouched for three months. Same project. Same full-time job. Same number of hours in a day. What changed: he had a deadline. A milestone definition. A daily prompt that asked a specific question about his specific project — not generic advice about “staying consistent.” And a check-in that made him write down what he actually built. Day 13: GitHub Pages live. 532 waypoints loaded into Litchi. KML and KMZ export working. DJI Air 2S ready for field use. Not a polished SaaS. Not a growth-hacked landing page. A working tool that does the thing it’s supposed to do, deployed, usable, real.
The gap between “I know how to build this” and “I shipped this” is not a knowledge gap. You already know enough. You’ve known enough for months. Six months ago you said two more weekends. Your GitHub has commits to a project nobody has ever used. You’re not blocked. You’re just not shipping. And if you’re being honest with yourself, you know the difference. AI gives you the plan. Nobody generates your discipline for the next 30 days. The execution layer is still entirely yours.
If you want to look at what’s actually blocking you — not in theory, not in a journaling exercise, but in 30 minutes with someone who’s watched this pattern up close — there are 3 slots open this week at mvpbuilder.io/diagnostic. USD 29. What’s blocking you.
