I Have 200 Unfinished Projects and That's Fine

I just counted. I have 200+ unfinished projects across various tools, folders, and half-deployed URLs. A meal planning app that's 60% done. A client portal that works but looks terrible. Three different attempts at a personal website. An AI tool that generates workout plans that I used exactly twice. A habit tracker with no habit tracking.

The productivity gurus would call this a problem. "You need to learn to finish what you start." "Discipline is choosing to do the boring work after the exciting newness wears off." "A finished bad project is worth more than an unfinished good one."

They're wrong. Or at least, they're missing the point.

Every unfinished project taught me something

That meal planning app? That's where I learned how to connect a database. I didn't finish the app, but I can connect a database now. That skill has shown up in six other projects.

The client portal? That's where I figured out user authentication. The three personal websites? Each one taught me something about design, deployment, or SEO that I now use everywhere.

Each unfinished project was a class I paid for with time instead of money. And unlike actual classes, I only studied the parts I was interested in.

The "finish everything" myth

This advice comes from a pre-AI era when building things was hard and slow. If a project took 6 months, yeah, you should probably finish it — you've already invested massive time and energy.

But in 2026? You can build a working prototype in 2 hours. The cost of starting something new is almost zero. Why would you force yourself to grind through the boring parts of project #47 when you could start project #48 and learn something new in the process?

The game has changed. The goal isn't to finish things — it's to learn fast and build skills. Unfinished projects are evidence of learning, not evidence of failure.

When finishing matters

I'm not saying never finish anything. Obviously if you're building for a client, finish the work. If you have paying users, maintain the product. If you're close to something genuinely useful, push through.

But that side project you started last Tuesday that you're already losing interest in? Let it go. Start something else. The code doesn't care about your commitment issues.

The portfolio of attempts

Here's what my 200 unfinished projects actually represent:

• -200 times I had an idea and acted on it
• -200 times I learned something new
• -200 different technologies, patterns, and approaches I've been exposed to
• -A breadth of experience that no single project could provide

When someone asks me if I can build something, I almost always say yes — not because I've done that exact thing before, but because I've done 12 things that are kind of like it. That only happens when you start a lot of projects.

Start another one

If you're sitting there with 50 unfinished projects feeling guilty about starting #51 — stop. Open your laptop. Start #51.

The best builders I know aren't the ones who finish everything. They're the ones who start constantly, learn aggressively, and occasionally — when something really clicks — see one through.

That's not a character flaw. That's a learning strategy.