Cloning GitHub in 49 Minutes
I cloned GitHub. Not a toy demo with three screens and a README viewer -- a full-featured, single-user Git hosting platform with repository management, code browsing with syntax highlighting, pull requests with three merge strategies, issues with labels and comments, releases, search, activity feeds, insights, dark mode, and 50+ API endpoints. 111 files. 18,343 lines of code. 155 passing tests. The whole thing took 49 minutes, entirely within the scope of a Claude subscription.
Using Claude to Clone Confluence in 16 Minutes
Day three. Another SaaS subscription, another Single Serving Application. I've now replaced Harvest (time tracking) and Trello (project management) with AI-generated clones. Today's target: Confluence -- Atlassian's knowledge management and wiki platform. Claude Opus 4.6 built a fully functional Confluence clone in 16 minutes, consuming 106,000 tokens. That's the fastest build yet -- down from 18 minutes for Harvest and 19 for Trello. The pattern is holding: requirements in, working application out, no human intervention needed.
Using Claude to Clone Trello in 20 Minutes
Last week I had Claude Opus 4.6 and GPT-5.3-Codex race to build a Harvest clone. Claude won decisively. That experiment killed a $180/year SaaS subscription. Naturally, I started looking at my other subscriptions. Trello was next on the list. I've used it for years to manage personal projects, product roadmaps, and random ideas. It's a great product -- but it's also a multi-tenant, collaboration-heavy platform where I use maybe 20% of the features. A perfect candidate for a Single Serving Application. So I wrote a requirements document, handed it to Claude Opus 4.6, and walked away. 19 minutes and 137,000 tokens later, I had a fully functional Kanban board running on localhost.
Ephemeral Apps Are Almost Here
I recently built a Harvest clone in 18 minutes, a Trello clone in 19 minutes, and a Confluence clone in 16 minutes. All three were generated entirely by Claude Opus 4.6 from requirements documents. All run in Docker. All work.
Single Serving Applications - The Clones
I'm systematically replacing my SaaS subscriptions with Single Serving Applications -- purpose-built, AI-generated apps designed for an audience of one. Each clone is built by Claude Opus 4.6 from a requirements document, runs via Docker Compose, and costs essentially nothing to operate.
The Single Serving Application
I recently had two AI models build a complete Harvest clone in under 20 minutes. The winning version covered 97% of Harvest's features. I'm seriously considering canceling my $180/year subscription and using it instead. That experiment got me thinking about something bigger than one app replacement. We're entering an era where a competent engineer with an AI coding assistant can generate a fully functional web application from a requirements document in the time it takes to eat lunch. That changes the economics of software in a fundamental way.
Claude Opus 4.6 vs GPT-5.3-Codex: Building a Full Web App From Scratch
Last week was a big week for Anthropic and OpenAI. Both released new versions of their flagship coding models: Claude Opus 4.6 from Anthropic and GPT-5.3-Codex (Medium) from OpenAI. Any time new coding models are released, it's like an extra Christmas for me. There was some talk about Sonnet 5.0 being released also but so far, nothing. I'm wondering if that has anything to do with the most recent agentic coding benchmarks.
Rebuilding My Site with Narrative CMS
Twenty years ago, I built a blogging platform called Narrative. It was an ASP.NET-based CMS with advanced features like automatic page rebuilding, a sophisticated tagging system, and comment spam prevention. I used it to power this site from 2003 until 2008, when I abandoned it in favor of WordPress, saying "I am much more interested in blogging than the building of blogging software." That code sat shelved for nearly two decades. Then, in 2024, I discovered Claude Code and realized something profound: with AI assistance, I could finally bring Narrative back to life—not as a compromise, but as exactly the system I'd always envisioned. This post tells that story.
