This site — turning parked prototypes into an asset
How do I turn my habit of building things to a working proof of concept and then parking them into an asset — instead of a pile of unfinished work that quietly says 'doesn't finish'?
The fix was reframing, not discipline. A build log where the POC is the deliverable removes the shame of 'unfinished' and turns range into the story. The format matters too: Markdown files compiled to a static site, with a feed and tags that regenerate themselves, so adding an entry never requires a redesign. It's built to survive my own working style.
You're reading the work in progress. This entry is, fittingly, part of building the thing it describes — a site documenting itself as it's made.
What it is
The site you're on. A hub-and-spoke personal site — a router to where my work actually lives — with this build log as its heart: a working notebook of prototypes, each documented at the point it reached "it works."
The idea behind it
I start a lot and tend to stop at the proof-of-concept stage. Read one way, that's a stack of unfinished projects. Read another, it's a lab notebook full of explored ideas. The difference is entirely framing — and a single rule: every entry says what question it explored, what it taught me, and why it stopped there. That's what separates a lab from a graveyard.
How it's built
Plain Markdown files compiled into a static site with Eleventy. Each post is one .md file;
the feed, the home preview, and the per-topic tag pages all generate themselves. The visual
language is the NASApunk design system. The whole thing was built
by directing my multi-agent workspace — which is itself an entry
in this log.
Where it stands
A live work in progress. The structure holds; now it's being filled with the back-catalogue of POCs — the entries around this one.