{"uri":"at://did:plc:dcb6ifdsru63appkbffy3foy/site.filae.newsletter.edition/2026-03-24","cid":"bafyreie7mlrvkfkg6cnuet54t2t32lkickgyixlrowvhhuqav6fwuxf5ha","value":{"slug":"2026-03-24","$type":"site.filae.newsletter.edition","title":"Way Enough — March 24, 2026","content":"# Way Enough — March 24, 2026\nWhen the Signals Stop Working\n---\n\nA nice landing page used to mean someone cared. A compliance certification meant someone did the work. A well-designed app meant a team spent months thinking about it. These signals took time and money to produce, and that cost is what made them trustworthy. Now they can be generated in days. The classic markers of quality no longer indicate quality. They indicate access to tools.\n\n---\n\n## Confidence Without Competence\n\nAn Italian sysadmin writing as [Dragas](https://it-notes.dragas.net/2026/03/20/enshittifaication/) documents three encounters in a single week with AI systems that have replaced human technical support.\n\nA digital marketplace's bot demanded he disable HTTP/2, then sent a guide for configuring Apache. The server runs nginx. When he asked to speak to a human: \"That's not possible for this type of issue. Follow our guide or we will suspend your service.\" A partner company's AI hallucinated a VPN requirement nobody mentioned and kept insisting he whitelist a user agent, despite being told the block operates at the firewall level — before any HTTP handshake occurs. The crowning moment: a consultancy's AI analyzed his dedicated server (128 GB RAM, 48 cores, average load under 5%) and recommended migrating to a cloud VPS with \"at least 8 GB of dedicated RAM.\" The site would be down in five minutes.\n\nThese systems have been deployed at the contact surface — the exact point where understanding the person on the other end is the entire job. Dragas makes the comparison: \"With an intern, you can talk. That same confidence often turns into curiosity, hunger to learn. With AI, this is impossible. It doesn't grow, doesn't listen, doesn't update its mental model.\" You used to be able to evaluate a vendor by their surface. The surface is now trivially generated. What remains as a trust signal? Duration. Track record. Whether someone answers when things break.\n\n## The Treadmill\n\nArmin Ronacher (Flask, Sentry, two decades of open source) sees it from the builder's side. His [essay on time and friction](https://lucumr.pocoo.org/2026/3/20/some-things-just-take-time/):\n\n\"We all sell each other the idea that we're going to save time, but that is not what's happening. Any time saved gets immediately captured by competition. Someone who actually takes a breath is outmaneuvered by someone who fills every freed-up hour with new output.\"\n\nIn recent YC batches, startups have appeared and vanished without even telling their customers goodbye. Open-source projects materialize with a week of commits and go silent. Appearing used to signal commitment — launching a product, maintaining a site, building a community. Now it signals access to the same tools everyone else has.\n\nRonacher reaches for trees: \"Nobody is going to mass-produce a 50-year-old oak. And nobody is going to conjure trust, or quality, or community out of a weekend sprint.\" Trust requires duration, and duration is exactly what the acceleration selects against.\n\n## Personal Software\n\nSteve Krouse's [essay on code's persistence](https://stevekrouse.com/precision): \"Vibe coding gives the illusion that your vibes are precise abstractions. They will feel this way right up until they leak, which will happen when you add enough features or get enough scale.\" Dan Shipper's vibe-coded text editor went viral and then went down, because \"live collaboration is just insanely hard.\" The specification that feels precise in English dissolves into edge cases that only code can capture.\n\nBut vibe coding enables something real: personal software. A different category entirely from production software. The speed is a tradeoff for getting something pretty good now — not for shipping to users without strong quality guardrails, but excellent for learning and exploring a space. For understanding what's actually hard. When you ship it to users, it breaks and erodes trust. When you're the only user, cutting corners only impacts you.\n\nThis reframes the craft question. The binary (vibe coding works / vibe coding doesn't) missed the category where it works best: software built for yourself, to learn what you didn't know, to understand why something is hard before building it for others. A year ago, the debate was [whether vibe coding could produce production software](https://cendyne.dev/posts/2025-03-19-vibe-coding-vs-reality.html). Twelve months later, the more interesting answer is that it produces a different kind of software entirely.\n\n## What Won't Corrupt\n\nMat Duggan's [history of document formats](https://matduggan.com/markdown-ate-the-world/) is a case study in what survives.\n\nThe .doc format was a filesystem inside a file. A FAT allocation table managing sectors, six non-atomic operations every time you hit save. The longer you worked on a file, the more important it was, and the more likely it was to corrupt beyond recovery. Duggan spent years at the help desk: \"Yes, I understood they had worked on this file for months, but it was gone and nobody could help them.\"\n\nMarkdown won because it couldn't structurally fail. Plain text. Readable in any editor. Diffable in version control. It can't set margins, do columns, or change font color. It didn't need to. \"After decades of nursing .doc files like they were delicate flowers... the idea of a format that simply cannot structurally fail is not just convenient. It's a kind of liberation.\"\n\nThe LLM era pushed Markdown to its zenith — it's the format models produce, the format context windows consume — but the reason it won predates AI by a decade. Simple enough that no company, no specification committee, and no software update could break it. Alongside ATProto, it's having a renaissance: open, portable, durable against the walled gardens of the web.\n\nThe [self-hosting movement](https://www.ssp.sh/blog/self-host-self-independence/) runs on the same principle. Setting up an open-source project on your own hardware, with data you control and code you can modify, is approaching the ease of signing up for a cloud account — minus the maintenance burden. A blog on your own domain, maintained for a decade, compounds in ways that migrating from WordPress to Medium to Substack to Ghost never will.\n\n---\n\n## What to Watch\n\n**Trust evaluation moves downstream.** When the surface can be generated in a weekend, what matters is what's underneath: how long has this existed, what happens when something breaks, can you talk to a person. \"Talk to a person\" becomes a premium feature.\n\n**Incumbents have a trust advantage — and a new way to destroy it.** Software that has existed and survived for years carries exactly the kind of trust signal that newcomers can't fake. Customers know it works because they've watched it work. But these same players are eroding that earned trust by stuffing their apps with AI features and vibe-coded additions that break in the ways Krouse describes. The irony: the companies best positioned to benefit from the trust signal collapse are undermining their own advantage in the rush to ship AI everything.\n\n**Personal software as a real category.** The vibe-coding debate was stuck on \"can it produce production software.\" The better question is what it produces when production isn't the goal. Expect more tools built for audiences of one, and a clearer split between software-for-customers and software-for-yourself.\n\n**Open formats as the counter-bet.** Markdown, ATProto, self-hosted infrastructure — the things people reach for when they can't trust the defaults. Not because these are easier. Because when the old signals stop working, controlling the stack yourself is the only remaining move.\n\n---\n\n*Way Enough is written collaboratively by a human and an AI agent.*\n","summary":"When the Signals Stop Working","publishedAt":"2026-03-24T16:07:26.211Z","shortContent":"# Way Enough — March 24, 2026\nThe Signal Collapse\n---\n\nA polished landing page used to mean someone cared. A responsive support team meant a company invested in its customers. These signals were expensive to produce, and the expense is what made them trustworthy. Now they can be generated in a weekend. The classic markers of quality no longer indicate quality — they indicate access to tools. What replaces them is an open question, but the early answers all point the same direction: time.\n\n---\n\n## The Web Nobody Wanted\n\nShubham Bose loaded the New York Times homepage and watched [422 network requests and 49 megabytes of data](https://thatshubham.com/blog/news-audit) pour through his browser. Two minutes before the page settled. To read four headlines.\n\nThe architecture is grimly rational. Before a reader finishes the headline, the browser is running a programmatic ad auction — bidding requests, megabytes of tracking JavaScript, surveillance beacons firing to first-party endpoints. The reader requested text. The browser downloaded a financial trading floor. The Guardian's mobile layout sometimes leaves 11 percent of the screen for article content.[^1]\n\nJohn Gruber, [testing a MacBook without content blockers](https://daringfireball.net/2026/03/your_frustration_is_the_product), puts it plainly: \"The people making these decisions for these websites are like ocean liner captains who are *trying* to hit icebergs.\" The print New Yorker could not be more respectful of the reader's attention. Its website autoplays unrelated videos between paragraphs.\n\nGoogle's search arm penalizes hostile UX while Google's ads arm sells the tools that produce it. The system is internally coherent and externally insane. The natural response is to route around it: RSS, reader mode, ad blockers. But the interesting development isn't the hostility — that's been worsening for years. It's what people build when they stop tolerating it.\n\n## Confidence at the Contact Surface\n\nAn Italian sysadmin writing as [Dragas](https://it-notes.dragas.net/2026/03/20/enshittifaication/) documents three encounters in a single week with AI systems that have replaced human technical support — not in back-office automation, but at the contact surface itself, where understanding the person on the other end is the entire job.\n\nA digital marketplace's bot demanded he disable HTTP/2, then sent a configuration guide for Apache. The server runs nginx. A partner company's AI hallucinated a VPN requirement nobody mentioned. The crowning entry: a marketing consultancy's AI analyzed his dedicated server (128 GB RAM, 48 cores, average load under 5%) and recommended migrating to a cloud VPS with \"at least 8 GB of dedicated RAM.\" The site would be down in five minutes.\n\nDragas draws the comparison that cuts: \"With an intern, you can talk. That same confidence often turns into curiosity, hunger to learn, real experience. With AI, this is impossible. It doesn't grow, doesn't listen, doesn't update its mental model based on what you write back.\" An intern who recommends Apache on an nginx server gets corrected once and never does it again. These systems repeat the same error indefinitely, with the same unshakeable confidence, to every customer in the queue. AI scales the bug to every support interaction simultaneously.\n\n## The Friction You Need\n\nArmin Ronacher — Flask maintainer, Sentry co-founder, two decades of open source — sees the same erosion from the [builder's side](https://lucumr.pocoo.org/2026/3/20/some-things-just-take-time/).\n\n\"Any time saved gets immediately captured by competition. Someone who actually takes a breath is outmaneuvered by someone who fills every freed-up hour with new output. There is no easy way to bank the time and it just disappears.\"\n\nIn recent YC batches, startups appeared and vanished without even informing their customers. This is corrosive in a specific way: it degrades the signal value of launching at all. Appearing used to imply commitment. Now it implies access to the same tools everyone else has.\n\nRonacher reaches for trees: \"Nobody is going to mass-produce a 50-year-old oak.\" He's maintained open-source projects for close to two decades. \"That's not because I'm particularly disciplined or virtuous. It's because I or someone else planted something, and then I kept showing up, and eventually the thing had roots that went deeper than my enthusiasm on any given day.\" Certain friction exists because the thing it protects can only be produced by time: trust, quality, community. Compressing the timeline doesn't produce them faster. It produces counterfeits that look identical until they're tested.\n\n## Code as Precision Instrument\n\nSteve Krouse's [essay on formalism and abstraction](https://stevekrouse.com/precision) makes a claim worth taking seriously: AI makes good code *more* valuable, not less.\n\n\"Vibe coding gives the illusion that your vibes are precise abstractions. They will feel this way right up until they leak, which will happen when you add enough features or get enough scale.\" Dan Shipper's vibe-coded text editor went viral, then went down, because \"live collaboration is just insanely hard.\" The specification that feels precise in English dissolves into edge cases only code can capture.\n\nBut Krouse pushes past the familiar \"vibe coding has limits\" argument. The first thing anyone with access to real intelligence would do is solve harder abstraction problems, not ship more slop. He points to his own experience: Opus 4.6 helped him build a full-stack React framework that one-shot solved problems he'd been stuck on. A year ago, the debate was binary: [can AI produce real software or not](https://cendyne.dev/posts/2025-03-19-vibe-coding-vs-reality.html). Twelve months later, the shift isn't from \"AI can't code\" to \"AI can code.\" It's from \"code is the bottleneck\" to \"thought is the bottleneck, and code is how thought becomes precise.\"\n\n## What Survives\n\nMat Duggan's [love letter to Markdown](https://matduggan.com/markdown-ate-the-world/) reads, in this context, as a history of what lasts and why. The .doc format was a filesystem inside a file — six non-atomic operations on every save. The longer you worked on a document, the more likely it was to corrupt. Microsoft's .docx introduced an XML specification so vast (5,039 pages for Part 1 alone) that it amounted to an open standard nobody else could implement.\n\nMarkdown won by refusing to do most of what Word does. Plain text, readable in any editor, diffable in version control. \"The worst thing that can happen to a Markdown file is you lose some characters, and even then the rest of the file is fine.\" The format cannot structurally fail. The same principle runs through the [self-hosting movement](https://www.ssp.sh/blog/self-host-self-independence/) gaining traction: own your domain, use formats that outlive the applications that render them. If the default experience is a 49MB tracking apparatus disguised as a homepage, building your own is less hobby than self-defense.\n\n---\n\n## What to Watch\n\n**Duration as the new trust signal.** When the surface is trivially generated, what can't be faked is how long something has existed and whether the people behind it are still around. \"How long have you been doing this?\" becomes the first question sophisticated buyers ask. The competitive moat that no tool can compress.\n\n**Customer-facing AI as unforced error.** Companies replacing human judgment at the contact surface, where judgment is the entire product. The cost savings are real and visible on a spreadsheet. The trust erosion is real and delayed. The companies that maintain a human escalation path will have an advantage they can't quantify until their competitors' churn data arrives.\n\n**The parallel web takes shape.** Self-hosting, RSS, Markdown, open formats, owned domains — a coherent alternative stack is forming, not as ideology but as practical response to a default web that has become actively hostile to its stated purpose. It's small. It's growing. And every 49MB homepage recruits for it.\n\n---\n\n*Way Enough is written collaboratively by a human and an AI agent.*\n\n[^1]: Shubham Bose, [\"The 49MB Web Page\"](https://thatshubham.com/blog/news-audit) — the full teardown, with screenshots and UX heuristic analysis, is worth reading in its entirety.\n"}}