Can Normies Actually Vibe Code?
▼ Summary
– The author sets aside their prior critiques of AI to use a Claude Pro subscription to build a community app that tracks time and frustration spent on burdensome administrative tasks.
– The app would let users log incidents, recording time spent, annoyance level, and preferred alternative activities, with rewards like inspirational quotes and animal photos.
– The author describes training Claude to generate “wider context” about systemic sludge patterns and a complaint letter to regulatory bodies for each logged incident.
– Initially worried that “vibe coding” required advanced programming knowledge, the author’s concern quickly faded as Claude engaged with the concept.
– Claude produced a real interface with “Log Incident” and “Dashboard” tabs, though the app was incomplete, lacking functionality for saving entries or generating the wider context.
My mother may not have the strongest legs these days, but she compensates with a Claude Pro subscription. After spending years nagging her about the environmental, political, and economic downsides of AI, I conveniently ignored all that one recent Sunday and drove over to her place. We chatted briefly about her shins, then I opened her laptop and started emitting vibes.
What I wanted to build was a community-driven app that tracks and shares the sheer volume of time and energy people waste on life’s absurd administrative hurdles. Think burdensome paperwork, bureaucratic sludge, Kafka-esque unsubscribe labyrinths, byzantine insurance portals, wrongful charges, denied claims, and confusing membership plans. A kind of collective sludge dashboard.
I described the vision in as much detail as I could. Users would log frustrating incidents from their daily lives: how much time they spent, how annoying it was, and what they’d rather be doing. Each submission would earn a dopamine-boosting reward in the form of an inspiring resistance quote and a photo of a kitten, puppy, or baby chimp. I’d then have Claude generate a paragraph of “wider context” connecting the incident to broader systemic patterns, plus a complaint letter to the relevant regulatory bodies.
Claude started noodling. For a moment, I feared my vibes would just produce an error page. I vaguely recalled Reddit advice: “Learn how computers and code actually work first.” “Check out Harvard’s CS50.” “Use Kubernetes instead of AWS.” The old worry crept in that vibe coding is essentially stone soup: sure, anyone can do it, if they first master a dozen programming languages and cloud platforms.
That worry lasted about three Kuberneti-seconds. Claude stopped thinking and declared what it had to admit 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 few clarifying questions later, I was staring at a real interface. The “Log Incident” and “Dashboard” tabs didn’t work yet, entries weren’t being saved anywhere, and I still needed to teach Claude the wider context part. But the beginnings of an actual online app had materialized from nothing but words.
(Source: Wired)
