Skip to content

MNMatthew Nolan

Failures

Things that didn’t work.

Not self-deprecation. Proof of iteration. Each one changed how I build.

All failures

Shelved Oct 3, 2026

I shipped a product nobody asked for

What happened: ClarityOS launched as a complete product: site, app, sign-in, payments. It got zero traffic and zero interest.
What it taught me: Shipped is not the same as wanted. I’d spent my hours on the product and almost none on finding the people it was for.
What changed: I shelved it, moved its best ideas into LOADLESS, and now treat distribution as part of the build.

Sept 15, 2026

A session overwrote my system’s memory

What happened: My AI sessions share one state file. One of them replaced the whole thing (28K of infrastructure history) with a single note on one topic.
What it taught me: Any file that many writers touch needs a rule, not just a backup.
What changed: I recovered it from a session backup and added a rule at the top of the file: append, never replace. Every session reads that rule first.

Oct 1, 2026

I deployed the wrong folder and every page went blank

What happened: In one of my experiments, the build put files one folder deeper than I deployed from. Every route returned 404. The homepage only looked alive because an old copy was cached at the edge.
What it taught me: Checking a page once isn’t verification. A cache can lie to you.
What changed: “Deployed” now means checked three separate ways: the real URL, the deployment’s own URL, and a real browser.

Oct 7, 2026

One product, too many copies

What happened: ClarityOS ended up with several repositories and duplicate deployments. Nobody, including me, could say for sure which one was real.
What it taught me: Sprawl is a quiet cost. Every extra copy is a future wrong answer.
What changed: Picked one canonical repo, deleted five duplicate deployments, and added a naming check that refuses new deploys that don’t follow the convention.

Built something that didn’t work? Let’s compare notes.

I’m looking for people who are building something, solving something, or seeing a problem differently.