Why I stopped overthinking and just started building

There's a version of me that spent three months planning a project that never shipped. Endless architecture diagrams, perfect folder structures, and the "right" tech stack. Sound familiar?

Here's what I learned: done is better than perfect.

The trap of over-planning

I used to think that more planning meant better outcomes. It doesn't. It often means analysis paralysis — you keep refining the plan until you've convinced yourself it's not ready yet.

The real learning happens when you're in the trenches. When you hit that weird bug at 2 AM. When you realize your "perfect" architecture doesn't scale. When users tell you they wanted something completely different.

What changed

I started shipping small. A minimal version. A proof of concept. Something that works, even if it's ugly.

The feedback loop is everything. You can't get feedback from a plan. You get it from something people can touch, use, break.

The new rule

If it takes more than a week to plan, start building instead.

Not every project needs this. But if you're like me — someone who loves the comfort of planning — try it. Ship something incomplete. Learn from it. Iterate.

Your future self will thank you.