The next article initially appeared on Drew Breunig’s weblog and is being republished right here with the writer’s permission.
In 1998, Eric S. Raymond printed the founding textual content of open supply software program improvement, The Cathedral and the Bazaar. In it, he detailed two strategies of constructing software program:
- The cathedral mannequin is rigorously deliberate, closed-source, and managed by an unique group of builders.
- The bazaar mannequin is open, clear, and community-driven.
The bazaar mannequin was enabled by the web, which allowed for distributed coordination and distribution. Extra folks might contribute code and share suggestions, yielding higher, safer software program. “Given sufficient eyeballs, all bugs are shallow,” Raymond wrote, coining Linus’s regulation.
The concepts crystallized in The Cathedral and the Bazaar helped kick off a quarter-century of open supply innovation and dominance.
However simply because the web made communication low-cost and birthed the bazaar, AI is making code low-cost and kicking off a brand new period full of idiosyncratic, sprawling, cobbled-together software program.
Meet the third mannequin: The Winchester Thriller Home.
The Winchester Thriller Home
Positioned lower than 10 miles southeast from the Pc Historical past Museum, the Winchester Thriller Home is an architectural oddity.
Following the dying of her husband and mother-in-law, Sarah Winchester managed a fortune. Her shares within the Winchester Repeating Arms Firm, and the dividends they threw off, made it so Sarah couldn’t solely reside in consolation however pursue no matter ardour she desired. That keenness was structure.
Sarah didn’t construct her mansion to accommodate ghosts1; she constructed her mansion as a result of she preferred structure. With no license, no formal coaching, in an period when ladies (even very wealthy ladies) didn’t have a path to practising structure, Sarah targeted on her own residence. She made up for her lack of license with ardour and successfully limitless funds.
Sarah constructed what she wished. “At its largest the home had ~500 rooms.” At present it has roughly 160 rooms, 2,000 doorways, 10,000 home windows, 47 stairways, 47 fireplaces, 13 loos, and 6 kitchens. Carved wooden drapes the partitions and ceilings. Stained glass is in every single place. Initiatives had been deliberate, accomplished, deserted, torn down, and rebuilt.
It was something however aimless. And sensible improvements ran all through, together with push-button gasoline lighting, an early intercom system, steam heating, and indoor gardens. The eccentricities that amuse right this moment’s guests had been principally sensible lodging for Sarah’s well being (stairways with very small steps), useful designs now not used (entice doorways in greenhouses to route extra water), or fast fixes to wreck from the 1906 earthquake.
Winchester handed in 1922. 9 months later, the home turned a vacationer attraction.
At present, many programmers are Sarah Winchester.
What occurs when code is affordable
We aren’t as wealthy as Sarah Winchester, however when code is that this low-cost, we don’t have to be.
Jodan Alberts illustrated this just lately, gathering and visualizing knowledge detailing public GitHub commits attributed to Claude Code. That’s his knowledge within the chart above, with Claude seeming to solely speed up by means of March.2
It’s exhausting to get a deal with on particular person utilization although, so I went looking for a proxy and landed on the chart under:
After Opus 4.5 and up to date work enabling Agent Groups, the common internet strains added by Claude per commit is now easy and regular at 1,000 strains of code per commit.3
1,000 strains of code per commit is ~2 magnitudes greater than what a human programmer writes per day.
Should you seek for human benchmarks, you’ll discover many citing Fred Brooks’s The Legendary Man Month whereas claiming an excellent engineer may write 10 cumulative strains of code per day.4 Should you additional discover, you’ll discover numbers greater than 10 cited, however typically lower than 100.
Right here’s an excellent anecdote from antirez on a Hacker Information thread discussing the Brooks “quote”:
I did some trivial math. Redis consists of 100k strains of code, I wrote a minimum of 70k of that in 10 years. I by no means work greater than 5 days per week and I take 1 month of holidays yearly, so assuming I work 22 days each month for 11 months:
70000/(22 x 11 x 10) = ~29 LOC / day
Which isn’t too removed from 10. There are days the place I write 300-500 LOC, however I suppose that a whole lot of work went into rewriting stuff and fixing bugs, so I rewrote the identical strains repeatedly over the course of years, however but I feel that this ought to be taken into consideration, so the Legendary Man Month ebook is certainly fairly correct.
Six years after this remark, Claude is pushing 1,000 strains of code per commit.
So what will we do with all this low-cost code?
Sadly, every little thing else stays roughly the identical price and roughly the identical pace. Suggestions hasn’t gotten cheaper; the “eyeballs” that guided the software program developed by the bazaar haven’t caught as much as AI.
There is just one supply of suggestions that strikes on the pace of AI-generated code: your self. You’re there to immediate, you’re there to assessment. You don’t must recruit testers, run surveys, or handle design companions. You simply construct what you need and use what you construct.
And that’s what many builders are doing with low-cost code: constructing idiosyncratic instruments for ourselves, guided by our passions, style, and wishes.
Sound acquainted?
Welcome to the thriller home
Steve Yegge’s Fuel City is a Winchester Thriller Home. It’s extremely idiosyncratic and sprawling, wealthy with metaphors and hacks. It’s the proper instrument for Steve.
Jeffrey Emanuel’s Agent Flywheel is a Winchester Thriller Home. A big subset of tokenmaxxers resolve they should rebuild their dependencies in Rust; Jeff is one such instance. His “FrankenSuite” contains Rust rewrites of SQLite, Node.js, btrfs, Redis, pandas, NumPy, JAX, and Torch.
Philip Zeyliger famous the sample final week, writing, “Everyone seems to be constructing a software program manufacturing facility.” But it surely goes past software program. Gary Tan’s private AI committee gstack is a Winchester Thriller Home constructed principally from Markdown.
In every single place you look, there are Winchester Thriller Homes.
Every Winchester Thriller Home is idiosyncratic. They’re extremely personalised. The tightly coupled suggestions loop between the coding agent and the consumer yields software program that displays the developer’s wishes. They normally lack documentation. To outsiders, they’re inscrutable.
Winchester Thriller Homes are sprawling. Guided by the wants of the developer, these instruments are likely to unfold out, consistently annexing territory within the type of new capabilities and new repositories. Work is sort of all the time additive. Code is added when it’s wanted, bugs are patched in place, and numerous appendages stay. There’s little incentive to prune when code is free.
And constructing a Winchester Thriller Home ought to be enjoyable. Coding brokers flip every little thing right into a facet quest, and we eagerly take part. Constructing the proper workflow is a ardour for a lot of devs, so we preserve pushing.
Winchester Thriller Homes are idiosyncratic, sprawling, and enjoyable. However does this imply we’re abandoning the bazaar?
What occurs to the bazaar?
What occurs once we all are likely to our thriller homes? When our free time is spent constructing instruments only for ourselves, will we cease engaged on shared initiatives? Will we abandon the bazaar?
Most likely not. The bazaar is packed proper now, however not in a great way.
Code is affordable, so individuals are slamming open supply repositories with agent-written contributions, in an try and pad their résumés or manifest their pet options. Daniel Stenberg ended bug bounties for curl after a deluge of poor submissions sapped reviewer bandwidth. It’s gotten so unhealthy, GitHub just lately added a characteristic to disable pull request contributions.
Anecdotally, I’m seeing good contributions choose up as nicely. They’re simply drowned out by the slop. For what it’s value, curl commits are dramatically up within the agentic period. And folks are sharing what they construct. A current evaluation by Dumky reveals packages and repos rising within the final quarter.
There’s loads of finances for each thriller homes and the bazaar when code is this low-cost. The brand new problem is creating techniques and processes for managing the deluge. We don’t want eyeballs to seek out bugs in the software program; we’d like eyeballs to seek out bugs earlier than they attain the software program.
In some ways that is the inverse of the bazaar mannequin period. The web made suggestions and communal coordination quicker, simpler, and cheaper. The bazaar mannequin has a excessive throughput of suggestions (many eyeballs) however comparatively excessive latency for modifications (file a difficulty, focus on, submit a PR, await assessment, and so forth.).
Coding brokers, then again, make implementation quicker whereas suggestions and coordination are unchanged. The Winchester Thriller Home mannequin sidesteps this by collapsing the suggestions loop into one particular person: Latency is close to zero, however throughput is simply you. The bazaar, outlined by communal work, can’t undertake this hack. Coding brokers within the bazaar create a multitude: implementation at machine pace hitting coordination infrastructure constructed for human pace. Which is why maintainers really feel like they’re drowning.
We want new instruments, abilities, and conventions.
Classes from the thriller home
Coding brokers have dropped the price of code so dramatically we’re getting into a brand new period of software program improvement, the primary change of this magnitude for the reason that web kicked off open supply software program. Change arrived rapidly, and it’s not slowing down. However in reviewing the Winchester Thriller Home framework, I feel we are able to take away a couple of classes.
Lesson 1: The bazaar and Winchester Thriller Homes can coexist.
When itemizing instance Winchester Thriller Homes, I didn’t point out OpenClaw, although it’s the defining instance. I saved it for right here as a result of it properly illustrates how Winchester Thriller Homes and the bazaar can coexist.
OpenClaw is extremely modular and locations few limitations on the consumer. It integrates 25 completely different chat and notification techniques, plugs into most inference finish factors, and is constructed on the exceptionally versatile pi agent toolkit. This keen flexibility was embraced early—safety and knowledge protections be damned—however since its exponential adoption Peter Steinberger and the group have been steadily pushing enhancements and fixes.
And like different breakout open supply initiatives of yore, the ecosystem is adopting the very best concepts and mitigating the worst elements of OpenClaw. Numerous alternate “claw” initiatives have emerged. (There’s NanoClaw, NullClaw, ZeroClaw, and extra!) Firms have launched providers to make claws simple or safer. Cloudflare launched Moltworker to make deploy simple, Nvidia shipped NemoClaw with a safety focus, and Claude retains including claw-like options to its desktop app.
Lesson 2: Don’t promote the enjoyable stuff.
One motive OpenClaw works so nicely within the bazaar is that it’s a basis for private instruments. Out of the field, a claw simply sits there. It’s as much as the consumer to find out what it does and the way it does it, leveraging the connections and infrastructure OpenClaw gives. OpenClaw lets much less skilled builders spin up their very own Winchester Thriller Homes, whereas skilled devs get to leverage a lot of the frequent integrations and techniques OpenClaw gives. Peter and group have completed an awesome job drawing a line between the frequent core (what the bazaar works on) and what they go away as much as the consumer: The boring, essential stuff is the job of the commons.
Considering again to Sarah Winchester and her idiosyncratic, sprawling mansion, we see the identical sample. Sarah employed distributors! She used off-the-shelf elements! Her bathtubs, bathrooms, taps, and plumbing weren’t crafted on website.
The boring stuff, the exhausting bits, or the issues which have disastrous failure modes are the issues we should always collaborate on or make use of specialists to deal with. (Come to assume, plumbing checks all three packing containers). That is the chance for open supply software program, dev instruments, and software program corporations.
Don’t attempt to promote builders the stuff that’s enjoyable, the stuff they need to construct. Promote them the stuff they keep away from or don’t need to take accountability for. Sarah Winchester didn’t rent metalworkers to craft the pipes for her plumbing, however she did rent craftspeople to create tons of of stained-glass home windows to her specs.
Lesson 3: The boundaries of code are communication.
OpenClaw reveals the bazaar stays related but in addition highlights the issues going through open supply within the agentic period. Proper now, there are 1,173 open pull requests and 1,884 new points on the OpenClaw repo.
There’s extra code and extra initiatives than we might ever assessment. The problem now, for open supply maintainers and customers, is sifting by means of all of it. How do we discover the novel concepts that everybody ought to undertake and borrow?
OpenClaw is without doubt one of the successes, one thing we all observed. And for it, the issue is processing the suggestions. For the initiatives we’ll by no means discover, those misplaced within the deluge, their drawback is lack of suggestions. You both discover consideration and drown in contributions or drown within the ocean of repos and by no means hear a factor.
The web made coordination low-cost and gave us the bazaar. Coding brokers made implementation low-cost and gave us the Winchester Thriller Home. What we’re lacking are the instruments and conventions that make consideration low-cost, that allow maintainers take up contributions at machine pace and let good concepts floor among the many noise. Till we determine this out, the bazaar will preserve getting louder with out getting smarter, and the very best concepts in our thriller homes will probably be forgotten as soon as we cease sustaining them.
