The dog that ushered me into the technological future was “low and thick.” That’s all my mother registered before it T-boned her in a city park earlier this year: dense, heavy, and traveling fast enough to fracture her right tibia. But enough about her. Let’s discuss what this set in motion in my life: Having successfully learned nothing about coding for two and a half decades, I would soon be attempting my very first software development project.

If you’ve ever had a low and thick dog break your mom’s shin bone, you know the stream of lesser indignities that follows. Case in point: the hours my father spent navigating phone trees, trying to manage my mom’s medical care. Are frustrating telephone calls significant in the grand scheme of things? No. But that stupid dog had chosen a technologically interesting moment to do its thing. For the first time in history, a problem no longer needed to be serious to bring serious tools to bear.

For as long as Silicon Valley has been selling a frictionless tomorrow, we ordinary people have been its passive shoppers—scrolling the App Store, hoping someone has gone to the trouble of building whatever we need. Enter AI and its democratizing sidekick: vibe coding. If the promise is real, suddenly we can build our own apps, as niche and trifling as we please, with zero programming skills. We merely gesture toward whatever irks us and a constellation of large language models, code generators, and development environments will click their heels.

Niche and trifling? That’s me! Where others vibe code résumé reviewers and inventory trackers and automated assistants to boost their work productivity, I had a different target in mind. Over the past couple years I’ve grown particularly fixated, personally and professionally, on what the policy world calls sludge: the rising tide of tiny administrative obligations that increasingly seems to define modern existence—and corrode our ability to get anything done. The hassle of dealing with insurance, or connecting that insurance to your doctor, or staying on top of airline miles, or navigating your kid’s school portal. The steps required to dispute a charge, or unsubscribe from a streaming service you forgot you had. Each of these feels like its own discrete assault on our time. But they’re not discrete. They’re separate mushrooms sprouting from the same mycorrhizal network.

In a way this is a calibration issue. While bigger problems might at least theoretically attract attention—legislation, journalism, a Senate hearing—the smaller ones, too petty to litigate, simply become a fact of life. The arc of history may bend toward justice, but when it comes to fighting a one-dollar bank fee, it bends toward hold music.

Which is where the fantasy of vibe coding captured my attention. Those hassles aren’t just accidental byproducts of complexity; they’re often features. A confusing portal, a dropped call, a process just opaque enough to discourage follow-through. At scale, they function less like bugs than like policy. The app I envisioned would expose this phenomenon, make the cumulative weight of these obligations a little harder to ignore. The image I’d like you to summon is a field of mushrooms trembling.

What my mom lacks in healthy legs, she makes up for in a Claude Pro subscription. Having needled her repeatedly over the past couple years about AI’s environmental, political, and economic implications, I brushed all that aside on a recent Sunday and drove to her house. After a little tibia talk, I opened her computer and began emitting vibes.

I’d like to create a communally shared app that gathers and shares information related to how much time and energy we devote to fighting burdensome administrative tasks, bureaucratic sludge, Kafka-esque unsubscribe mazes, byzantine insurance portals, wrongful charges, denied claims, confusing membership plans, and the like.

With as much clarity and detail as I could muster, I proceeded to describe a dashboard that would record the scale and scope of our collective sludge. Users would log frustrating incidents from their lives, entering how much time they’d spent, how annoying it was, and what they’d rather have been doing. Every submission would be dopaminally rewarded with an inspiring resistance quote and a photo of a kitten, puppy, or baby chimp. I’d train Claude to generate some “wider context”—a paragraph discussing how the frustrating incident fits into systemic sludge patterns—and a complaint letter to the relevant regulatory bodies.

Claude noodled. Not for the first time, I feared my vibes would simply manifest an error page. I recalled, dimly, some of the advice I’d seen in Reddit forums: “I’d learn how computers and code works first.” “I’d look into going through harvards CS50.” “Instead of learning AWS or servers, use something like Kuberns.” I began to worry that vibe coding was a kind of stone soup: Sure, anyone can do it, you just first need a Harvard-level understanding of several dozen programming languages and cloud platforms.

That worry lasted about three Kuberns of a second. Claude stopped thinking and proceeded to explore what, by nature, it had to concede was an amazing concept: “This is a fantastic idea—genuinely useful, with a clear mission and a great sense of humor about a real problem. Let me give you an honest lay of the land before we dive in.”

A couple clarifying questions later, I was staring at a real interface. The “Log Incident” and “Dashboard” tabs didn’t work yet, we hadn’t arranged for the entries to be saved anywhere, and I still needed to teach Claude the wider context part. But the beginnings of an online app had materialized.

I spent the next hour ironing out kinks. Some fixes Claude could make, some it had me make. I understood nothing and was merely following orders (while also being the one who gave out the orders). But steadily we made headway, and help—confident, reassuring, clear—was always a whimper away:

ME: I got through step 3 above, but I’m getting confused at step 4. Here’s a screen shot of what I’m seeing after I clicked Settings.

CLAUDE: Good news - you’re in the right place, and very close. But I can see Supabase has updated their interface since I wrote those instructions. What you’re looking at is their new API keys screen, which is slightly different from what I described …

The experience was akin to building an elaborate Lego creation: You don’t know what each individual Ribbed Hose or Flared Mudguard does, but if you follow the directions to a tee, the thing does get built.

Linus Torvalds, Steve Wozniak, Bill Gates: I assume these guys could only borrow their moms’ computers for so long. After a couple hours, I told Claude we’d pick up again soon.

I drove home giddy—a giddiness I recognized from a brief arc-welding phase in my twenties. I can’t believe I, a regular person, can make this! For all the websites and apps I whip through on a given day, they’ve always been mysterious to me—pyramids erected by an unfathomable priesthood. Suddenly I was a pyramid builder.

I wasn’t alone. Someone in Florida had recently built something called Stratus, a guitar pedal that lets players describe an effect in plain English—“give me a wobbly tremolo with a warm Mellotron feel”—and generates it. Elsewhere a guy named Justin had built a Plywood Cutting Visualizer—enter the dimensions of a sheet, get back the cuts. Someone else had made MIXCARD, which turns your Spotify playlists into physical postcards. The barrier between idea and creation had, for a certain kind of person with a certain kind of afternoon, effectively dissolved.

But this was also the catch. What happens when anyone with a passing itch builds their own app? Those environmental, political, and economic concerns came roaring back—accompanied by a new worry.

Before the pandemic, I began having friends over for a ritual I called Admin Night. The idea is to power through your personal sludge in communion with others. One thing I noticed is that many of today’s administrative tasks are the residue of yesterday’s tech solutions—systems that promised to streamline our productivity or organize our memories, then broke or expired or began charging $14.99 a month. Would AI be different, or was I just assisting in the creation of more sludge?

A couple days later, I visited Mom again. My app was coming along, but the final stretch seemed to be taking as long as the first 90 percent. I needed accounts at GitHub (to store my code), Supabase (to store users’ sludge records), and Netlify (to serve the app), each straightforward, each an opportunity for error. I left my API key exposed in the public GitHub repository, for instance. Claude caught it and moved the key somewhere safe. Then there was security to ponder. My Instagram algorithm having grown wise to my new hobby, I’d been served a suggested prompt for app builders, one explaining how to compel Claude to run a security audit. Sure enough, we found that user-submitted text was being inserted into the page’s HTML unsanitized, meaning anyone could submit malicious code as their company name and it would execute in every visitor’s browser. Easy fix.

The tasks were menial but doable: ferrying credentials between services, clicking Deploy, watching something fail, pasting the error back to Claude, repeating. Assembly, not engineering—think Ikea daybed. I made three more visits to my mom’s house, and by the time her tibia was strong enough to try out crutches, my app was ready for a trial run.

I invited my dad over to the computer, interviewed him about that phone tree and typed his answer into the app—cathartic already for him, I noticed.

Whenever I call to make a doctor’s appointment, I have to sit through options that aren’t likely choices for patients calling to make an appointment—the very first being information for sending a fax. Also the claim that the menu options have changed recently seems unlikely. The whole system feels less efficient than it could be, and sitting through this recording again and again starts to add up and feel crazy-making over time.

How much time had he spent navigating this stuff? Three hours. How annoying was it? Three out of 10. What would he rather have been doing? Gardening.

My dad’s submission was rewarded with an Ursula K. Le Guin quote—“We live in capitalism. Its power seems inescapable. So did the divine right of kings.”—accompanied by a tiny dachshund napping beside a stream.

From there my auto-context generator went to work:

Automated phone systems typically front-load options based on call volume data or administrative convenience rather than user intent, which is why fax transmission—likely a legacy option serving a small percentage of callers—sits ahead of the appointment-booking function that probably generates most inbound traffic.

What’s more, it continued, the company could fix that dubious “menu options have changed recently” bit with some simple tweaks “that would cost little beyond someone’s time to implement but require treating patient friction as an actual problem worth solving.”

My father, while also just generally dazzled that I can operate a computer, was particularly impressed by this conjuring of perspective. But there was still an automated content moderation process for Claude and me to cook up. Now, before users’ submissions display in the public dashboard, they go through some fairly rigorous filters. (Good luck getting through, CrotchGoblin69.) Two days later I sent the URL to my Admin Night community; we exist because the sludge problem is communal, and any real answer has to be communal too. Soon they were submitting complaints about Audible’s credit policy, getting double-billed by Hulu, the log-in gymnastics required to buy a daughter’s prom ticket. One member, Danielle, likened the whole thing to a “grievance dragnet.” Another, Amy, told me it was “like a friend who comes over to listen to you cry about your latest breakup and then, while you are in the shower she’s strongly recommended, creates a new dating profile crafted to avoid all the things she has just heard you complain about.” Seeing the other entries in the app, she added, “was a reminder that it’s not you, it’s the system.”

The idea that the internet might redistribute power in a meaningful way has been giving cover to Big Tech and its enablers since forever, and I have no illusions that a blast of amateur coding will claw back our time and agency from the purveyors of sludge. Nevertheless, my blast of amateur coding is now live on Netlify. For all I know it will crash tomorrow. But it undeniably exists—a shared civic ledger where once there was only frustration. Sludge thrives on exhausting us in the dark and the assumption that our individual wasted hours don’t add up to anything. They do. I’ve got a janky database to prove it.

Maybe I’ve internalized Claude’s inane affirmations, but I was struck by what a few hopeful vibes could summon. In less trifling hands, there’s no telling what these tools could do, are doing now. For once, maybe the menu options really might change.

Let us know what you think about this article. Submit a letter to the editor at [email protected].