I built 128 things with AI in 4 months. Then I made an AI dissect all of it.

I’m 19. In four months I built 128 projects with AI — 61 GitHub repos, 15 MCP servers, a 7-department agent OS, the works.

I shipped 5. Total stars: 6. Revenue: $0.

That gap bothered me enough that I did the obvious-but-uncomfortable thing: I had an AI audit everything — every repo, every project folder, 4,239 build sessions, 244 memory notes — and pin it all like specimens in a cabinet. No flattery. Here’s what the autopsy found.

→ The full interactive atlas: https://builder-archive.vercel.app/en

The number that explains everything

128 built. 5 shipped.

It’s tempting to read that as a discipline problem. It isn’t. The build velocity is real — I once shipped ~20 vertical SaaS in a single weekend on a shared Next.js + Drizzle + Stripe stack. The code works. The UIs are clean.

The problem is the last mile. README writing, deployment, the final 10% that turns a repo into a thing a stranger can use — that’s where almost everything died. Not ability. Execution.

The AI put it in one line:

“Can build anything. Finishes nothing.”

Strength and weakness are the same coin

Here’s the part I didn’t want to see: the thing that makes me fast is the thing that kills me.

Because I can build deep, I lose the stopping point. Because building is cheap, I start the next thing before finishing the last. The audit scored two skill axes:

• Build (design → implementation → automation): advanced
• Distribution (publish → ship → monetize): beginner

Every problem I have lives in that asymmetry. It’s not a motivation gap — total commits across repos: ~4,800. The effort is enormous. It just never crosses the finish line into something public.

The hardest thing I made is the one I hid

The audit flagged a buried asset: a GCC/ZATCA e-invoicing toolkit — Saudi Fatoora Phase 2, EN16931 + Peppol validation, secp256k1 signing, Go compiled to WASM. The single hardest, most verifiable piece of work I’ve done.

It’s been sitting in a private repo.

That’s the disease in one example: the more valuable the thing, the more likely I am to leave it in the dark. Scale ≠ shipped. An 80MB project with zero users taught me that the expensive way.

What the autopsy actually changed

Three things came out of pinning 128 specimens to a board:

1. One hard rule: no new project until one existing thing is shipped to distribution. The strength (build depth) only becomes an asset when the weakness (finishing) is forced.
2. The build history itself is the asset. “A 19-year-old built 128 things with AI and shipped almost none” is, weirdly, a more honest and more interesting story than any single product. So I made it the product.
3. Publishing is the first move, not the last. This article — and the atlas it links to — is me finally doing the thing the audit said I never do.

The atlas

Everything above is one interactive page: a build timeline, a causal project graph, the dead projects with causes of death, the buried assets, a leveled skill tree, viral/reputation/proof/asset scores per project, and three TOP-10 lists (what could go viral in 30 days, build credibility in 1 year, become an asset in 3). It even auto-generates a 6-part video documentary from the history.

→ https://builder-archive.vercel.app/en

If you’re a builder who also makes more than you finish: the fix isn’t more discipline. It’s forcing the narrow thing. Kill 127 ideas, ship the 1.

Built faceless under greymoth. Cold-honest, no growth-hacking — just the autopsy.

Written by **greymoth. I build developer tools and write about where software quietly breaks — Japanese/CJK edge cases, i18n, the boring infra nobody checks. → *glovrex.com** · github.com/greymoth-jp*