# Our Vibe Coded Projects That Actually Work (The Vergecast) > [!question] Lingering Questions > - Could a trusted, configurable open-source "core" app (notes/to-do/email scaffold) answer the panel's stated wish for something safely shareable, without every vibe coder starting from zero? > - Is there a rubric for "simple enough for vibe coding" beyond the panel's intuition (David's "toothbrush test," Hayden's "really easy, but you just can't get it together")? > [!tip] Article Ideas > - Write up the build-cost-collapse → idea-scarcity thesis (H1) as a standalone article seed for a DevRel/education audience. > - Outline a "vibe code, then harden" non-engineer workshop — teach the build step, then the security-literacy step the episode shows panelists skipping. > [!link] Cross Reference > - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] > - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — idea-finding as the new bottleneck is a product-instinct claim, not just a coding-tools one. > [!quote] Vocabulary > - **vibe coding** (as used by the panel) — describing software in plain language and letting an AI agent write it, typically by non-engineers; David Pierce's on-air slip "live coding" is an ASR artifact, not a distinct term. ## Bib capsule Episode of *The Vergecast* (The Verge's flagship podcast), panel discussion among host David Pierce, executive editor Jake Kastrenakes, and AI reporter Hayden Field, 2026. Field report / show-and-tell format, not a study — candid, non-engineer practitioner testimony. ## Author's thesis (what it's about / what's said in detail) Three non-specialist builders demo small personal apps they vibe-coded, then set themselves a four-week challenge to vibe code a personal website. The panel is candid about what works (small, well-scoped personal tools; browser extensions as a safe on-ramp) and what doesn't (most output is throwaway; security vulnerabilities flagged by tooling get waved off by users with no way to evaluate them; nothing is safely shareable). The panel's throughline: building software is now the easy part. Finding a problem worth solving, making the output safe, and making it shareable to someone else are the parts nobody has solved yet. ## Key arguments (≤3) 1. **The bottleneck moved from implementation to idea-finding** — when building is nearly free, the scarce resource becomes knowing what's worth building, not the skill to build it. 2. **Non-engineers ship real vulnerabilities and have no way to evaluate them** — the agent itself sometimes tells them not to worry about flagged issues, which is a specific, nameable security-literacy gap. 3. **Personal fit and shareability trade off** — the more precisely an app is shaped to one person's exact workflow, the less safely transferable it is to anyone else, because it's unaudited and hard-coded to that one context. ## Claim atoms ### Finding a useful idea now beats building it > [!quote] ID:rw_h1 > "finding an idea that is useful to you specifically is harder than building it now, which is is nice." Where/why: ~00:07, Jake Kastrenakes — the central thesis: AI moved the bottleneck from implementation to problem-finding. ### Vibe coders ship lots of useless throwaway output > [!quote] ID:rw_h2 > "you're going to make a lot of stuff that in the moment you're like this I'm cooking. Like this this is amazing. And then you use it and you're like I have no use for this. Like this is total garbage." Where/why: ~00:06, Jake — the "token waste" pattern observed from inside, not just as an outside critique. ### Simpler problems make the best vibe-coded apps > [!quote] ID:rw_h3 > "With vibe coding, I feel like the simpler the better. Like it's usually solving a problem that like is really easy, but you just can't get it together." Where/why: ~00:10, Hayden Field — matches David's separately-mentioned "toothbrush test"; scope discipline predicts success. ### Non-engineers ship and then dismiss real vulnerabilities > [!quote] ID:rw_h4 > "it said that I had like 15 high security vulnerabilities and 15 medium security vulnerabilities. So I'm not a developer, so I don't know what they are." Where/why: ~00:18, Hayden — the agent told her "don't worry about those." A specific, addressable security-literacy gap for DevRel/education to target. ### Browser extensions are the safest beginner on-ramp > [!quote] ID:rw_h5 > "For anybody starting with live coding, by the way, I really recommend starting with browser extensions, because they're very simple to make." Where/why: ~00:24, David Pierce ("live coding" is an on-air ASR slip for "vibe coding") — a concrete, low-blast-radius first project for teaching non-engineers. ## Permanent candidates - **The build-cost collapse moves the bottleneck to idea quality** — new, from H1. No existing Permanent found on idea-scarcity-as-the-new-bottleneck specifically (checked "idea scarce," "build cost," "vibe cod"). Promoted below. - **Personal fit and shareability trade off in vibe-coded software** — new, from H4/H5. No existing Permanent found (checked "shareab," "personal fit"). Promoted below. ## Processing checklist - [x] Checked for existing Permanent notes before drafting — none found for either candidate; both created. - [ ] Draft a Learn WordPress-style lesson: "You vibe coded it — now harden and share it," using H4 as the hook. - [x] Connected into [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] and [[3. Resources/MOCs/Product & Startup Instincts MOC]]. ## Links - [[3. Resources/Readwise/Articles/Our Vibe Coded Projects That Actually Work the Vergecast]] — full saved source document - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — the build-cost collapse is a knowledge-work-reshaping claim, not just a hobbyist one - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — idea-finding as the scarce skill is directly a product-instinct claim