Not 5. Not 10. Twenty.
That's how many folders I counted in my Projects directory last month. Each one with a README, a few commits, sometimes a deployed demo. All of them dead somewhere between "this is the best idea I've ever had" and "I should really get back to this."
For a long time I blamed discipline. Then I blamed my job being too draining. Then I blamed context-switching. Then I read four books about habits and built elaborate productivity systems that I also abandoned.
None of it touched the actual problem.
The actual problem was that I had never identified which specific psychological mechanism was generating the abandonment. And without knowing that, I was treating symptoms.
Here's what I found after going pretty deep into behavioral psychology research.
The pattern I was actually running
I'm what the research calls a "Paralyzed Visionary." High idea-generation rate. Genuine excitement at the start of projects. Tendency to keep multiple options open instead of committing to one.
The mechanism underneath: choosing one project felt like closing the door on all the others. And the brain reads irreversible choice as loss. So it keeps generating new ideas — not because it's creative, but because new ideas reopen the optionality. They're a defense against commitment.
I didn't have too many ideas. I had an aversion to finality disguised as creativity.
The other 6 patterns
Once I understood mine, I found 6 others that cover essentially every developer I've talked to since:
The Perfectionist — never ships because the bar keeps moving. The real driver is fear of judgment, not standards.
The Dopamine Chaser — starts everything, finishes nothing. The brain got its reward from solving the core problem. Why ship?
The Over-Researcher — is always learning, never applying. Research is socially safe avoidance.
The Impostor — comparison as a veto. "Someone else is doing this better" as an excuse not to start.
The Invisible Player — builds things nobody ever sees. Ships privately to a vault.
The Loyal Prisoner — circumstance as a permanent excuse. Real constraints, functioning as a permission structure for inaction.
What actually helped
Not a productivity system. Not a new habit tracker.
Understanding which pattern I was running — specifically, not generally — and addressing the psychological function it was serving.
When I stopped trying to "get more motivated" and started asking "what is this avoidance protecting me from," the answer was uncomfortable and also useful.
I built a 7-question diagnostic to identify which pattern is yours: psychoprompt.netlify.app
Curious — what's in your project graveyard?
Top comments (0)