An engineer barely read the DNS server Claude wrote; a reader checked it live
Josh Bleecher Snyder spent about a week having Claude design and rebuild exe.dev's distributed DNS server, then said in his write-up that he'd read almost none of the resulting code. In the comments, a reader ran a live query against the system's actual DNS records to see if the story held up.
exe.dev's original single-region DNS server kept breaking as it expanded, so Josh Bleecher Snyder had Claude design and build the distributed replacement almost solo. He reports zero incidents since, and says Claude ran the whole project end to end, calling the practice 'vibe-engineering.'
The thread didn't take that framing on faith. A reader ran a live dig query against exe.dev's own DNS records to check his fix, and a principal engineer countered that prompt instability, not wrong answers, means an LLM can never really be a compiler.
The DNS server that got built while its owner barely watched
Josh Bleecher Snyder runs engineering at exe.dev, a startup that spins up disposable VMs in seconds through an AI assistant it calls Shelley, each one landing on its own subdomain like my-app.exe.xyz. The VMs boot so fast that DNS couldn't keep up, so exe.dev wrote its own DNS server to fix propagation delays. Then it added regions, and the single US server became the new bottleneck, breaking a little on every deployment. In his own words:
"We did what a sensible engineer does when faced with a hard problem: cheat. We vibe-engineered a distributed DNS server tuned to our specific needs." — from the original post
Building the replacement took about a week of Snyder's attention, he says, and produced zero DNS incidents the month after launch. Claude researched distributed-DNS designs, ran concurrent agent loops to build the system and its tests, compared candidate implementations against each other, and went through three rounds of what Snyder calls "differential spec analysis" — matching the written spec against what actually got built. The output was a "scar-tissue document," his term for an accumulated, battle-tested guide detailed enough to steer an agent through both architecture and low-level decisions. His conclusion, quoted directly in the thread:
"I read a vanishingly small amount of the actual code… I'd say that, in all the ways that matter, I understand the code. Sure, if I had to hand-edit it now, there'd be a serious learning curve. But I won't have to." — from the original post
His larger claim is that Claude isn't a compiler translating instructions into code. It's a "vertically integrated resource" working from strategy down to implementation, a practice he calls vibe-engineering.
Where the "Claude is a compiler" line actually came from
Several early replies asked, reasonably, whether anyone with real standing had ever actually claimed Claude is a compiler, since the whole post exists to argue against that idea. One answer was sitting in the piece's own opening line:
"The title is a reference back to 'Is Claude Code a Compiler?' by the same author… The hands-down highlight was the talk by Erik Schluntz: Vibe coding in prod. Among other things, he drew an analogy between LLMs and compilers." — a reader who linked directly to the original post and the talk it cites
So the metaphor this post spends its length dismantling didn't arrive from an outside skeptic. It came from inside the same conversation, a year earlier, at the talk that prompted Snyder's first essay on the subject.
A reader checked the DNS fix against the live system
Some pushback stayed technical instead of rhetorical. One reader decided to check exe.dev's DNS fix against the live domain rather than take the post's word for it:
"exe.xyz has a fairly short 10 second negative TTL, so even if you tried to resolve it before it was set up in the authoritative DNS, it wouldn't stay negative-cached very long…
dig +short soa exe.xyz
ns1.exe.dev. hostmaster.exe.dev. 1854440 86400 7200 1209600 10" — a reader who ran a live dig query against exe.dev's own DNS records
The number matched the architecture Snyder described, a detail nobody else in the thread had bothered, or been able, to verify independently.
Why a principal engineer says the compiler metaphor can't hold
The sharpest theoretical objection came from a voice with real domain weight:
"The non-determinism is theoretical solvable. Chaos (prompt instability) isn't. When you change a single word in the input, you get a completely different output. Because of this LLMs will never be compilers." — a principal engineer at a supply-chain unicorn, currently writing a book on network programming
A distributed-systems engineer pushed the disagreement further back, past the compiler metaphor to the premise underneath it:
"LLM-is-a-compiler is indeed a simplistic approach. I wrote a rebuttal to yesterday's Cursor post, may reuse it here… Specs do not appear out of nowhere, they co-evolve with the code. If you have the code, why do you want to generate it again?" — an engineer who works on CRDTs and distributed systems, who says he made the identical argument the day before about an unrelated AI-coding post
The real disagreement in the thread was never about compiler semantics. It was about verification. Snyder trusted a week of Claude's decisions and a scar-tissue document he wrote himself; a reader trusted a dig command against the live domain instead. If vibe-engineering becomes normal practice, checking someone's homework may end up looking less like reading their code and more like querying their infrastructure directly.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
A West African Coral Reef Sat Buried in a Report for 60 Years
In the 1960s, fishing surveyors off Benin hauled coral heads up in their nets and noted it in one paragraph of a report nobody read again. Sixty years later, a Beninese researcher borrowed a fishing pirogue, towed a sonar rig behind it, and found the reef still thriving in the dark water below.