[{"data":1,"prerenderedAt":1544},["ShallowReactive",2],{"blog-is-vibe-coding-bad":3,"related-is-vibe-coding-bad":393},{"id":4,"title":5,"author":6,"body":7,"category":6,"date":378,"description":379,"draft":380,"extension":381,"image":6,"meta":382,"navigation":383,"path":384,"seo":385,"stem":386,"tags":387,"__hash__":392},"blog\u002Fblog\u002Fis-vibe-coding-bad.md","Is Vibe Coding Bad? When It Works (And When It Doesn't)",null,{"type":8,"value":9,"toc":359},"minimark",[10,19,24,27,38,41,45,48,55,64,68,75,121,125,128,138,142,145,152,160,164,167,170,179,183,192,195,199,202,213,216,230,233,237,240,243,247,250,263,267,270,300,303,307,310,314,317,328,336,340,343,352],[11,12,13,14,18],"p",{},"The phrase \"vibe coding\" started as a joke and became a workflow. Ask an AI to build something, squint at the output, describe what feels wrong, repeat. It's fast, it's fun, and for a certain class of work it's genuinely productive. But the question \"is vibe coding bad\" doesn't have a yes-or-no answer. It has a ",[15,16,17],"em",{},"where"," answer. Vibe coding is fine for some things and quietly catastrophic for others, and the line runs straight through the middle of anything you plan to ship as a real product.",[20,21,23],"h2",{"id":22},"what-is-vibe-coding-and-why-developers-keep-arguing-about-it","What Is Vibe Coding (And Why Developers Keep Arguing About It)",[11,25,26],{},"Vibe coding is letting an AI generate code without detailed specs, then iterating on feel. You don't write an architecture document. You write a prompt, look at the result, and nudge it toward what you want.",[11,28,29,30,37],{},"It exploded because Claude and GPT made it feel frictionless. The term itself was coined by Andrej Karpathy, who ",[31,32,36],"a",{"href":33,"rel":34},"https:\u002F\u002Fx.com\u002Fkarpathy\u002Fstatus\u002F1886192184808149383",[35],"nofollow","described it"," as giving in to the vibes and forgetting the code even exists. Prompt engineering replaced the architecture doc for a lot of people.",[11,39,40],{},"The appeal is real. Fast feedback loops. Discovery-driven development where you learn what you want by seeing it. A much lower barrier for solo builders who never had a team to lean on. None of that is fake. The problem is what happens after the vibe becomes a codebase.",[20,42,44],{"id":43},"the-real-problem-instructions-become-obsolete-instantly","The Real Problem: Instructions Become Obsolete Instantly",[11,46,47],{},"Here's the uncomfortable part. The moment an AI generates code from your prompt, that prompt becomes a historical artifact. It's not documentation. It's a fingerprint of a decision you can no longer see.",[11,49,50,51,54],{},"The code becomes the only source of truth for what the system does. But code doesn't explain ",[15,52,53],{},"why"," a decision was made. It doesn't tell you that the refund path assumes webhooks arrive in order, or that a particular query only works because a row-level security policy is written a certain way.",[11,56,57,58,63],{},"For a solo weekend project, that's survivable. For a SaaS with billing, auth, and webhooks, it's a slow-motion disaster. The answer isn't to stop using agents. It's to give them a contract that survives iteration — which is exactly why BoiledPlate ships an ",[31,59,62],{"href":60,"rel":61},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fconventions-for-ai-coding-agents",[35],"AGENTS.md file that documents one way to do data access and secrets",", so the agent can't quietly invent a fourth.",[20,65,67],{"id":66},"where-vibe-coding-fails-hard","Where Vibe Coding Fails Hard",[11,69,70,71,74],{},"The failures cluster around anything with ",[15,72,73],{},"state",".",[76,77,78,91,97,103,109,115],"ul",{},[79,80,81,85,86,74],"li",{},[82,83,84],"strong",{},"Billing."," Stripe webhook idempotency breaks the instant you regenerate the handler on a vibe. Refund logic drifts. Your ",[31,87,90],{"href":88,"rel":89},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-webhooks-source-of-truth",[35],"checkout success page starts touching billing state it should never touch",[79,92,93,96],{},[82,94,95],{},"Auth and RLS."," Row-level security needs deliberate schema design, not experimentation. Vibe-coded policies leak data.",[79,98,99,102],{},[82,100,101],{},"Multi-tenant data."," One wrong policy and customer A sees customer B's records, or you orphan rows nobody can reach.",[79,104,105,108],{},[82,106,107],{},"Email flows."," Transactional email needs idempotency keys so a retried webhook doesn't send the same receipt twice. Vibes ignore this.",[79,110,111,114],{},[82,112,113],{},"Deployment and config."," Environment variables and secrets scatter across a dozen generated files with no single owner.",[79,116,117,120],{},[82,118,119],{},"Consent."," EU withdrawal law, GDPR, cookie consent — vibes get these wrong immediately, and the mistake is a legal one, not a compilation error.",[20,122,124],{"id":123},"why-vibe-coding-works-for-toys-fails-for-products","Why Vibe Coding Works for Toys, Fails for Products",[11,126,127],{},"The difference is invariants. A product has things that must always be true: billing state is consistent, tenant data is isolated, audit trails exist. Vibe coding treats code as disposable. Products treat code as fragile and in need of guards.",[11,129,130,131,134,135,74],{},"Personal projects reward speed because a bug costs you five minutes. SaaS punishes surprise refactoring because a bug costs you a customer, a chargeback, or a regulator's attention. The dichotomy people reach for — \"vibe coding versus six-month waterfall\" — is false. The real choice is between ",[15,132,133],{},"intentional architecture"," and ",[15,136,137],{},"expensive bugs",[20,139,141],{"id":140},"the-imposter-syndrome-trap","The Imposter Syndrome Trap",[11,143,144],{},"Vibe coding sells a comforting lie: you don't need to understand the full stack. The AI has you covered.",[11,146,147,148,151],{},"The reality is the opposite. You need to understand it ",[15,149,150],{},"more",", because the AI won't catch your domain errors. It doesn't know your business rules. An agent vibe-coding a SaaS won't independently invent Stripe's signature verification or reason correctly about Supabase's RLS model — those are specific, non-obvious contracts.",[11,153,154,155,159],{},"This is where explicit conventions break the cycle. An agent handed clear constraints stops guessing. Without them, ",[31,156,158],{"href":60,"rel":157},[35],"it pattern-matches against every bad tutorial it has ever seen"," and adds its own fourth way of doing things.",[20,161,163],{"id":162},"vibe-coding-vs-deterministic-patches","Vibe Coding vs. Deterministic Patches",[11,165,166],{},"There's a better model than \"regenerate the module until it feels right.\" Deterministic patches: code changes that are repeatable, reversible, and documented.",[11,168,169],{},"Patches read like instructions. They're auditable. They don't drift, because they describe a specific transformation rather than a mood. Adding a new Stripe product should be a discrete, verifiable patch — not \"regenerate the whole billing layer while I describe the vibe I want.\"",[11,171,172,173,178],{},"Agents actually prefer this. A patch has a defined before and after they can verify. A vibe has neither. BoiledPlate's setup interview ",[31,174,177],{"href":175,"rel":176},"https:\u002F\u002Fboiledplate.ai",[35],"reshapes the codebase to your answers with deterministic patches"," precisely so nothing depends on the agent's mood on a given afternoon.",[20,180,182],{"id":181},"the-uncomfortable-truth-speed-vs-rigor-isnt-binary","The Uncomfortable Truth: Speed vs. Rigor Isn't Binary",[11,184,185,186,134,189,74],{},"You do not choose between vibe coding and endless architecture reviews. You choose between ",[15,187,188],{},"documented iteration",[15,190,191],{},"undocumented chaos",[11,193,194],{},"Fast shipping with RLS and webhook idempotency intact is entirely possible — if you have a contract. The contract is what lets speed and rigor coexist. Automate the plumbing, but make the automation verifiable.",[20,196,198],{"id":197},"small-projects-vs-shipping-saas-when-vibe-coding-works","Small Projects vs. Shipping SaaS: When Vibe Coding Works",[11,200,201],{},"Vibe coding is genuinely fine for:",[76,203,204,207,210],{},[79,205,206],{},"CLI tools, scripts, internal utilities",[79,208,209],{},"Throwaway prototypes you build to learn something",[79,211,212],{},"Solo exploration with no external dependencies",[11,214,215],{},"Vibe coding breaks for:",[76,217,218,221,224,227],{},[79,219,220],{},"Anything with state — databases, webhooks, billing",[79,222,223],{},"Code that other developers will inherit",[79,225,226],{},"Code an agent needs to update safely six months later",[79,228,229],{},"Anything involving customer data or payment flows",[11,231,232],{},"If your project is on the first list, stop reading and go vibe. If it's on the second, keep going.",[20,234,236],{"id":235},"why-ai-agents-amplify-vibe-codings-failures","Why AI Agents Amplify Vibe Coding's Failures",[11,238,239],{},"Agents follow patterns. Vibe code has no pattern to follow — it's a pile of one-off decisions with no through-line. So the agent invents one, and now you have two conventions where you wanted one.",[11,241,242],{},"Agents also can't ask about implicit decisions. They don't know that a webhook must be idempotent unless something tells them. They won't invent signature verification, correct RLS policies, or refund idempotency on their own. The fix is a standard, not more vibes.",[20,244,246],{"id":245},"building-saas-without-vibe-coding-the-plumbing-first-approach","Building SaaS Without Vibe Coding: The Plumbing-First Approach",[11,248,249],{},"Flip the order. Start with service provisioning, not code generation.",[11,251,252,253,256,257,262],{},"Establish RLS, Stripe webhooks, and email transactionality ",[15,254,255],{},"before"," the business logic. Let the agent wire services deterministically instead of guessing at configs. Then document the decisions so future changes don't quietly break assumptions. As BoiledPlate's team puts it, ",[31,258,261],{"href":259,"rel":260},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fhow-to-ship-saas-fast",[35],"the stack picks itself — the plumbing is the actual project",". Building that plumbing first is what makes the fun part safe.",[20,264,266],{"id":265},"what-shipping-a-real-product-teaches-you-about-vibe-coding","What Shipping a Real Product Teaches You About Vibe Coding",[11,268,269],{},"Real bugs teach faster than any argument. From actually shipping:",[76,271,272,281,289,297],{},[79,273,274,275,280],{},"A ",[31,276,279],{"href":277,"rel":278},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-page-that-returned-200-on-the-server-and-500-in-the-browser-a-json-ld-tempor",[35],"JSON-LD hydration crash that returned 200 on the server and 500 in the browser",", traceable to source order and canonical URL config.",[79,282,283,284,74],{},"Refund logic that only works if webhooks arrive in order — see ",[31,285,288],{"href":286,"rel":287},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-github-invite-is-the-product-building-a-stripe-webhook-where-delivery-throws",[35],"why some webhook failures must throw and some never can",[79,290,274,291,296],{},[31,292,295],{"href":293,"rel":294},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-checkout-consent-collection-german-withdrawal-waiver",[35],"German withdrawal waiver that has to be encoded into the pay button",", or you carry regulatory risk.",[79,298,299],{},"Peer dependency conflicts that surface six months later, long after the vibe that caused them.",[11,301,302],{},"The lesson is consistent: plumbing mistakes are expensive, and vibes don't catch them.",[20,304,306],{"id":305},"the-honest-take-when-to-use-vibe-coding-when-not-to","The Honest Take: When to Use Vibe Coding, When Not To",[11,308,309],{},"Vibe coding is a delivery mechanism, not a philosophy. Use it for rapid discovery, throwaway code, and learning. Don't use it for anything you'll ship, anything with state, or anything others will touch. The better alternative for real work is structured iteration with documented conventions.",[20,311,313],{"id":312},"how-to-ship-fast-without-vibes","How to Ship Fast Without Vibes",[11,315,316],{},"Speed doesn't have to come from abandoning structure. It can come from automation:",[76,318,319,322,325],{},[79,320,321],{},"Provision services in one session — the agent interviews you, then wires Stripe products and webhooks, a Supabase database with RLS, and Google sign-in.",[79,323,324],{},"Customize with deterministic patches instead of regenerating.",[79,326,327],{},"Keep an agent-readable contract so updates happen safely half a year later.",[11,329,330,331,335],{},"That's the whole bet: ",[31,332,334],{"href":175,"rel":333},[35],"everything a paid product needs on day one",", wired once and documented, so the fast part stays fast.",[20,337,339],{"id":338},"the-real-cost-technical-debt-vs-upfront-investment","The Real Cost: Technical Debt vs. Upfront Investment",[11,341,342],{},"Vibe coding is fast in month one and exponentially slower after, as undocumented decisions pile up. A structured approach is slower in week one and then linear — the cost of change stays flat because the assumptions are written down.",[11,344,345,346,351],{},"You will have bugs either way. The only question is whether they're discoverable or hidden. Vibe coding hides them behind confident-looking code. A contract like ",[31,347,350],{"href":348,"rel":349},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-saas-boilerplate-for-ai-agents",[35],"AGENTS.md drags them into the open"," where you can actually fix them.",[11,353,354,355,358],{},"So — is vibe coding bad? No. It's a tool. It's bad the same way a chainsaw is bad in a nursery. Use it where the stakes are low and the state is disposable. Everywhere else, give your agent a contract and let the plumbing be automatic ",[15,356,357],{},"and"," verifiable.",{"title":360,"searchDepth":361,"depth":361,"links":362},"",3,[363,365,366,367,368,369,370,371,372,373,374,375,376,377],{"id":22,"depth":364,"text":23},2,{"id":43,"depth":364,"text":44},{"id":66,"depth":364,"text":67},{"id":123,"depth":364,"text":124},{"id":140,"depth":364,"text":141},{"id":162,"depth":364,"text":163},{"id":181,"depth":364,"text":182},{"id":197,"depth":364,"text":198},{"id":235,"depth":364,"text":236},{"id":245,"depth":364,"text":246},{"id":265,"depth":364,"text":266},{"id":305,"depth":364,"text":306},{"id":312,"depth":364,"text":313},{"id":338,"depth":364,"text":339},"2026-07-12","Vibe coding with AI is fast and fun, but it has real limits. Learn when it's productive and when it quietly catastrophic for shipped products.",false,"md",{},true,"\u002Fblog\u002Fis-vibe-coding-bad",{"title":5,"description":379},"blog\u002Fis-vibe-coding-bad",[388,389,390,391],"vibe coding","AI code generation","software development","best practices","cRvFBRA4dX3jw2hqFd4Xm9mX2lmj1ypOGlKjeKnri5U",[394,894,1205],{"id":395,"title":396,"author":6,"body":397,"category":6,"date":882,"description":883,"draft":380,"extension":381,"image":6,"meta":884,"navigation":383,"path":885,"seo":886,"stem":887,"tags":888,"__hash__":893},"blog\u002Fblog\u002Fvibecoding-apps-promise-vs-reality.md","Vibecoding Apps: The Promise vs. Production Reality",{"type":8,"value":398,"toc":864},[399,407,410,414,417,420,439,442,446,449,452,464,468,471,497,500,505,565,569,572,610,613,617,620,627,640,644,647,655,658,684,687,691,702,705,709,712,746,749,753,756,776,779,783,815,819,827,831,834,838,845,849,855],[11,400,401,402,406],{},"Vibe coding has a clean pitch: describe your app in plain language, and an AI writes the code. The term went mainstream after Andrej Karpathy ",[31,403,36],{"href":404,"rel":405},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FVibe_coding",[35]," as \"fully giving in to the vibes\" and forgetting the code even exists. For prototypes, it genuinely works. For production SaaS with real billing and real users, the gap between \"it runs\" and \"it ships\" is where most vibecoding apps quietly stall.",[11,408,409],{},"This is an honest map of what vibe coding actually does, where the tools break, and how agent-guided building differs from one-shot generation.",[20,411,413],{"id":412},"what-vibe-coding-actually-is","What Vibe Coding Actually Is",[11,415,416],{},"Vibe coding is AI-assisted development where natural language drives code generation instead of traditional syntax. You describe intent; a model produces implementation.",[11,418,419],{},"But \"vibe coding\" is a spectrum, not one thing:",[76,421,422,428],{},[79,423,424,427],{},[82,425,426],{},"Pure description"," (Google AI Studio, Lovable): you type a goal, you get output.",[79,429,430,433,434,438],{},[82,431,432],{},"Agent-guided structured building"," (Cursor with conventions, ",[31,435,437],{"href":175,"rel":436},[35],"BoiledPlate","): an agent interviews you, then applies structured changes to a known codebase shape.",[11,440,441],{},"Both use natural language. Only one keeps producing coherent code past the first afternoon.",[20,443,445],{"id":444},"the-promise-vs-the-reality-gap","The Promise vs. the Reality Gap",[11,447,448],{},"Marketing says: describe your app, get a working product. What actually happens is: description → generated code → integration hell.",[11,450,451],{},"The generated code is usually the easy 10%. The other 90% is plumbing — the wiring between services that no demo ever shows. Stripe webhooks that agree with your database. Row-level security policies. Refund state. EU consent flows. i18n strings that have to land in five places before the build stops complaining.",[11,453,454,455,458,459,463],{},"Vibe coding fails silently here because a one-shot generator can produce a Stripe checkout button that ",[15,456,457],{},"looks"," done and has no working webhook behind it. It compiles. It even redirects. It just doesn't record the payment when the user closes the tab. As we've argued before, ",[31,460,462],{"href":259,"rel":461},[35],"the stack is easy and the plumbing is the project"," — and plumbing is exactly what one-shot tools skip.",[20,465,467],{"id":466},"vibe-coding-tools-an-honest-taxonomy","Vibe Coding Tools: An Honest Taxonomy",[11,469,470],{},"Four broad categories, each solving a different slice:",[76,472,473,479,485,491],{},[79,474,475,478],{},[82,476,477],{},"No-code visual builders"," (FlutterFlow, Canva Code): UI-first, limited backend logic. Fine for MVPs, high lock-in.",[79,480,481,484],{},[82,482,483],{},"Pure language-to-code"," (Google AI Studio, Lovable): fast initial output, weak at multi-service integration.",[79,486,487,490],{},[82,488,489],{},"Agent-guided structured builders"," (BoiledPlate, Cursor + strong conventions): interviews shape the infrastructure, deterministic patches keep the codebase coherent.",[79,492,493,496],{},[82,494,495],{},"Full-stack IDE environments"," (Replit, Bolt.new, Base44): sandboxed and impressive, but you still wire the real services yourself.",[11,498,499],{},"None of these is strictly better. They're built for different points in the lifecycle. The mistake is using an exploration tool for a production launch.",[501,502,504],"h3",{"id":503},"what-each-actually-solves","What each actually solves",[506,507,508,521],"table",{},[509,510,511],"thead",{},[512,513,514,518],"tr",{},[515,516,517],"th",{},"Need",[515,519,520],{},"Who handles it well",[522,523,524,533,541,549,557],"tbody",{},[512,525,526,530],{},[527,528,529],"td",{},"Rapid prototyping",[527,531,532],{},"All of them, inconsistently",[512,534,535,538],{},[527,536,537],{},"Production auth with RLS",[527,539,540],{},"Only tools with deterministic secrets + database-level permissions",[512,542,543,546],{},[527,544,545],{},"Real billing (idempotent webhooks)",[527,547,548],{},"Almost none in one-shot mode",[512,550,551,554],{},[527,552,553],{},"Multi-language i18n",[527,555,556],{},"Almost none automatically",[512,558,559,562],{},[527,560,561],{},"SEO (JSON-LD, canonicals, prerendering)",[527,563,564],{},"Only purpose-built frameworks",[20,566,568],{"id":567},"the-workflow-where-the-time-actually-goes","The Workflow: Where the Time Actually Goes",[11,570,571],{},"People imagine vibecoding apps is 90% prompting. In practice, for anything real:",[76,573,574,580,586,592,598,604],{},[79,575,576,579],{},[82,577,578],{},"Prompt clarity and iteration"," — 5–15% of time, but decisive.",[79,581,582,585],{},[82,583,584],{},"Reviewing generated code quality"," — 20–30%.",[79,587,588,591],{},[82,589,590],{},"Service provisioning"," (Stripe, Supabase, Google OAuth) — manual in most tools.",[79,593,594,597],{},[82,595,596],{},"Webhook architecture and idempotency"," — 30–40%. This is the real work.",[79,599,600,603],{},[82,601,602],{},"Edge cases"," — refunds, subscription transitions, EU withdrawal periods.",[79,605,606,609],{},[82,607,608],{},"Deployment and monitoring"," — always an afterthought.",[11,611,612],{},"The prompt is the smallest slice. The webhook is the biggest. That ratio is why \"describe your app\" undersells the job.",[20,614,616],{"id":615},"ai-agents-vs-vibe-coding-tools","AI Agents vs. Vibe Coding Tools",[11,618,619],{},"The core difference is memory and structure.",[11,621,622,623,626],{},"A vibe coding tool does one-shot generation with a limited context window and no persistent conventions. An agent working against a starter kit does iterative interviews, applies deterministic patches, and reads a contract that tells it how ",[15,624,625],{},"this"," codebase does things.",[11,628,629,630,634,635,639],{},"That contract matters more than it sounds. As we've written, ",[31,631,633],{"href":60,"rel":632},[35],"an agent cannot smell a codebase"," — give it three ways to fetch data and it cheerfully adds a fourth, because it has no reason to prefer yours. Without written conventions, every suggestion drifts a little further from the shape of your code. BoiledPlate ships an ",[636,637,638],"code",{},"AGENTS.md"," contract precisely so the agent reads one documented way to do data access and secrets, then respects your customizations instead of reinventing them.",[20,641,643],{"id":642},"the-billing-problem-nobody-solves","The Billing Problem Nobody Solves",[11,645,646],{},"This is where vibecoding apps break most predictably.",[11,648,649,650,654],{},"Client-side success pages lie. The user pays, the browser redirects, and then they close the tab before your success page finishes running. If your billing state depends on that page, you just lost a payment record. The only reliable source of truth is the Stripe webhook — ",[31,651,653],{"href":88,"rel":652},[35],"your checkout success page should not touch your billing state"," at all.",[11,656,657],{},"Doing this right requires:",[76,659,660,672,678],{},[79,661,662,665,666,671],{},[82,663,664],{},"Idempotent webhooks"," so a redelivered event doesn't double-charge or double-provision. Stripe ",[31,667,670],{"href":668,"rel":669},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks#handle-duplicate-events",[35],"explicitly recommends"," handling duplicate events.",[79,673,674,677],{},[82,675,676],{},"Refund and downgrade state machines"," — partial refunds, subscription changes, EU withdrawal windows.",[79,679,680,683],{},[82,681,682],{},"Stripe as the single source of truth",", with everything else a view of Stripe state.",[11,685,686],{},"Almost no one-shot tool encodes this. It requires ongoing architecture, not a single generation.",[20,688,690],{"id":689},"auth-and-security-where-it-breaks-quietly","Auth and Security: Where It Breaks Quietly",[11,692,693,694,697,698,701],{},"Row-level security is invisible in generated code and critical in production. A generator can wire Google sign-in flawlessly and still leave your database wide open, because sign-in only proves ",[15,695,696],{},"who"," the user is — RLS decides ",[15,699,700],{},"what rows"," they can touch.",[11,703,704],{},"Supabase RLS policies are auto-generated wrong more often than right. This is the classic \"a user saw someone else's data\" bug, and it never shows up in a demo because demos have one user. Agent-driven builders solve this by encoding RLS templates as part of the starter, not leaving each policy to a fresh guess.",[20,706,708],{"id":707},"real-world-bugs-in-generated-code","Real-World Bugs in Generated Code",[11,710,711],{},"Generated code fails in specific, repeatable ways:",[76,713,714,725,734,740],{},[79,715,716,719,720,724],{},[82,717,718],{},"JSON-LD hydration crashes"," in Nuxt SSR — a page that returns ",[31,721,723],{"href":277,"rel":722},[35],"200 from curl and 500 in the browser"," because of source order. A generator won't catch this; it's an integration bug, not a syntax bug.",[79,726,727,730,731,74],{},[82,728,729],{},"Canonical URL edge cases"," — trailing slashes, query params, and the memorable case of a blog telling Google its canonical URL was ",[636,732,733],{},"localhost:3000",[79,735,736,739],{},[82,737,738],{},"TypeScript strict mode"," — most generators skip it and hand you union-type nightmares.",[79,741,742,745],{},[82,743,744],{},"Peer dependency conflicts"," — Stripe SDK versions, Supabase auth breaking changes.",[11,747,748],{},"None of these are clever problems. They're endless, slightly different, and exactly the kind of thing that eats a launch weekend.",[20,750,752],{"id":751},"the-cost-equation","The Cost Equation",[11,754,755],{},"Realistic numbers matter more than hype:",[76,757,758,764,770],{},[79,759,760,763],{},[82,761,762],{},"Time to working prototype",": a couple of hours in Lovable; roughly an hour with a structured starter if the interview is clear.",[79,765,766,769],{},[82,767,768],{},"Time to production-ready",": add 2–4 weeks of plumbing regardless of tool.",[79,771,772,775],{},[82,773,774],{},"Cost of lock-in",": high with FlutterFlow and Canva Code, medium with Replit and Bolt, low with GitHub-native delivery where the code lives next to your CI\u002FCD.",[11,777,778],{},"The prototype gap between tools is small. The production gap is enormous, and it's decided by architecture, not by prompt quality.",[20,780,782],{"id":781},"choosing-a-tool-a-quick-matrix","Choosing a Tool: A Quick Matrix",[76,784,785,791,797,803,809],{},[79,786,787,790],{},[82,788,789],{},"MVP under a week",": Google AI Studio, Lovable, Canva Code.",[79,792,793,796],{},[82,794,795],{},"Production SaaS with billing",": an agent plus a strong starter kit, or manual work with agent oversight.",[79,798,799,802],{},[82,800,801],{},"Mobile-first",": FlutterFlow.",[79,804,805,808],{},[82,806,807],{},"Maximum flexibility",": Replit, Bolt.new — sandboxed, but you wire everything.",[79,810,811,814],{},[82,812,813],{},"Zero lock-in",": GitHub + Claude agent + a Nuxt\u002FSupabase\u002FStripe starter.",[20,816,818],{"id":817},"why-nuxt-supabase-stripe-works-for-agents","Why Nuxt + Supabase + Stripe Works for Agents",[11,820,821,822,826],{},"This combination isn't fashion; it's about predictable integration points. Nuxt's universal rendering forces deterministic patterns an agent can read and extend. Supabase RLS policies are template-able. Stripe webhooks give one unambiguous source of truth. Every SaaS starter ships this stack — but as we've noted, ",[31,823,825],{"href":348,"rel":824},[35],"that was never the hard part",". The parts are cheap; bolting them together is the project.",[20,828,830],{"id":829},"what-vibe-coding-wont-do-yet","What Vibe Coding Won't Do Yet",[11,832,833],{},"Be honest about the ceiling. Generated schemas are brittle, so migrations are risky. Updating generated code tends to break old queries. Vibe-coded apps are hard to inherit because no one wrote down the conventions, which means no one owns the plumbing. And AI-generated code against regulatory requirements is still a gray area.",[20,835,837],{"id":836},"where-vibe-coding-genuinely-shines","Where Vibe Coding Genuinely Shines",[11,839,840,841,844],{},"None of this means vibe coding is a fad. It is genuinely faster for exploration, for the prototype-to-feedback loop, and for grinding down repetitive boilerplate. The best use of an agent isn't \"build me a startup\" — it's \"given this codebase shape, what's the right next step?\" That question only has a good answer when the codebase ",[15,842,843],{},"has"," a documented shape.",[20,846,848],{"id":847},"conclusion-a-layer-not-a-replacement","Conclusion: A Layer, Not a Replacement",[11,850,851,852,854],{},"The real speedup in vibecoding apps isn't the initial generation — it's structured integration. The framework was never what slowed you down; the plumbing was. Use vibe coding tools for exploration, and use agent-guided starter kits for production, where deterministic patches and an ",[636,853,638],{}," contract keep output coherent past month three.",[11,856,857,858,863],{},"That's the model BoiledPlate is built around: an agent that interviews you, provisions Stripe, Supabase, and Google sign-in, and then respects your customizations instead of drifting away from them. You can read ",[31,859,862],{"href":860,"rel":861},"https:\u002F\u002Fboiledplate.ai\u002Fblog",[35],"more of the engineering log on the blog"," — every edge case it took to make the plumbing trustworthy is written down, because that's the part vibe coding still can't hand you for free.",{"title":360,"searchDepth":361,"depth":361,"links":865},[866,867,868,871,872,873,874,875,876,877,878,879,880,881],{"id":412,"depth":364,"text":413},{"id":444,"depth":364,"text":445},{"id":466,"depth":364,"text":467,"children":869},[870],{"id":503,"depth":361,"text":504},{"id":567,"depth":364,"text":568},{"id":615,"depth":364,"text":616},{"id":642,"depth":364,"text":643},{"id":689,"depth":364,"text":690},{"id":707,"depth":364,"text":708},{"id":751,"depth":364,"text":752},{"id":781,"depth":364,"text":782},{"id":817,"depth":364,"text":818},{"id":829,"depth":364,"text":830},{"id":836,"depth":364,"text":837},{"id":847,"depth":364,"text":848},"2026-07-19","Explore how vibecoding apps work, where they break down, and the gap between prototypes and production SaaS that actually ships with real users.",{},"\u002Fblog\u002Fvibecoding-apps-promise-vs-reality",{"title":396,"description":883},"blog\u002Fvibecoding-apps-promise-vs-reality",[889,890,891,892],"vibecoding","AI development","code generation","SaaS development","6xVs1JNK5DqaC2I5I7p7VIrAUYF6PkCHDYjGNHtBzOs",{"id":895,"title":896,"author":6,"body":897,"category":6,"date":1193,"description":1194,"draft":380,"extension":381,"image":6,"meta":1195,"navigation":383,"path":1196,"seo":1197,"stem":1198,"tags":1199,"__hash__":1204},"blog\u002Fblog\u002Fvibe-coding-gemini-production.md","Vibe Coding with Gemini: From Demo to Production Reality",{"type":8,"value":898,"toc":1177},[899,902,906,909,912,916,919,922,925,929,932,935,949,957,961,964,971,974,982,986,989,997,1004,1008,1016,1028,1040,1044,1047,1058,1062,1070,1094,1098,1106,1110,1113,1117,1120,1132,1138,1141,1145,1154,1158,1164,1168],[11,900,901],{},"Vibe coding is having a moment. Type a sentence, get an app. Google's pitch with Gemini in AI Studio is that anyone can describe a \"vibe\" and watch a working React app appear, then ship it to Cloud Run in minutes. It's genuinely impressive. It's also where most of the honest conversation stops. Because the distance between \"it runs on my screen\" and \"it survives paying customers\" is exactly the distance this article is about.",[20,903,905],{"id":904},"what-vibe-coding-actually-means","What \"Vibe Coding\" Actually Means",[11,907,908],{},"Vibe coding means turning natural-language prompts into functional code — not sketches, not pseudocode, but something that compiles and deploys. You describe the goal (\"a neon-themed pomodoro timer for my kid\") and Gemini writes it. People have built personalized apps in under 30 minutes this way, and the demos are real.",[11,910,911],{},"The gap is between \"describe your vibe\" and \"ships to production.\" Gemini positions this as democratized development: anyone can code now. What that actually requires, once you leave the single-file demo, is everything vibe coding quietly skips — billing state, data isolation, webhook retries, compliance. The framework was never the hard part.",[20,913,915],{"id":914},"gemini-vs-claude-the-agent-architecture-choice","Gemini vs. Claude: The Agent Architecture Choice",[11,917,918],{},"The two dominant coding-agent styles behave very differently, and it matters more than benchmarks suggest.",[11,920,921],{},"Gemini sprints. As one developer put it comparing it to Claude Code, \"Gemini doesn't make a plan and ask you if you want to proceed. It sprints ahead.\" That's fast and satisfying for a prototype. Gemini 2.5 Flash is faster still than Gemini 3 Pro, but developers who ran the same project through both found Flash more manual and more error-prone — speed traded against correctness.",[11,923,924],{},"Claude's agentic workflow leans the other way: plan first, then execute deliberate, repeatable changes. For a throwaway timer, planning is overhead. For a multi-tenant SaaS with billing, planning is the whole game. Consistency beats velocity the moment your codebase outlives the first session.",[20,926,928],{"id":927},"the-real-cost-of-fast-single-file-apps-vs-plumbing","The Real Cost of \"Fast\": Single-File Apps vs. Plumbing",[11,930,931],{},"A neon React timer in half an hour is a fair benchmark for what vibe coding covers well: UI components, basic logic, deployment scaffolding.",[11,933,934],{},"Here's what it doesn't touch:",[76,936,937,940,943,946],{},[79,938,939],{},"Signature-verified, idempotent Stripe webhooks",[79,941,942],{},"Row-level security so users can't read each other's rows",[79,944,945],{},"Refund flows that don't double-cancel on a retry",[79,947,948],{},"EU consent compliance baked into the pay button",[11,950,951,952,956],{},"None of that is clever work. It's endless, slightly-different-every-time work — the kind we call ",[31,953,955],{"href":259,"rel":954},[35],"plumbing",". And it's where launches actually stall. Vibe coding a UI is a solved problem. Wiring the services beneath it is the project.",[20,958,960],{"id":959},"building-real-apps-where-google-ai-studio-hits-a-wall","Building Real Apps: Where Google AI Studio Hits a Wall",[11,962,963],{},"Google AI Studio's newer vibe-coding experience can add databases and even multiplayer. That's progress, but \"add a database\" is where the real work starts, not where it ends.",[11,965,966,967,970],{},"Multiplayer requires state synchronization and, critically, ",[82,968,969],{},"row-level security"," so one user's writes never leak into another's session. A database alone gives you none of that — you still need a migration strategy, schema validation, and a policy layer enforced at query time.",[11,972,973],{},"Billing is worse. Provisioning Stripe products, verifying webhook signatures, and making handlers idempotent is not something a prompt reliably produces. And auth? Adding Google sign-in is trivial. Managing the user session, the RLS policies tied to it, and the secrets that must never reach the client is not.",[11,975,976,977,981],{},"This is exactly the box-of-parts problem we've written about before: ",[31,978,980],{"href":348,"rel":979},[35],"every boilerplate ships the stack",", then leaves you alone in a room with the wiring.",[20,983,985],{"id":984},"the-vibe-coding-workflow-that-actually-works-for-saas","The Vibe Coding Workflow That Actually Works for SaaS",[11,987,988],{},"The missing step in the \"describe it and deploy\" pitch is the interview.",[11,990,991,992,996],{},"Before an agent should touch a SaaS codebase, it needs answers: What's the billing model — one-time or subscription, how many plans? What user roles exist? What data must be isolated per tenant? BoiledPlate's setup runs exactly this way — ",[31,993,995],{"href":175,"rel":994},[35],"your coding agent interviews you",", then provisions Stripe, Supabase, and Google sign-in based on your answers.",[11,998,999,1000,1003],{},"Those answers drive ",[82,1001,1002],{},"deterministic patches",": automated, repeatable code changes that reshape the starter to your specific setup rather than hallucinating a fresh architecture each run. And validation matters — \"the code compiles\" is not \"the billing survives production.\" Those are two entirely different claims.",[20,1005,1007],{"id":1006},"webhook-architecture-the-plumbing-nobody-teaches","Webhook Architecture: The Plumbing Nobody Teaches",[11,1009,1010,1011,1015],{},"Here is the single lesson most vibe-coded billing systems get wrong: your checkout success page is not your source of truth. ",[31,1012,1014],{"href":88,"rel":1013},[35],"Stripe webhooks are",". The user can close the tab, lose signal, or refresh — the webhook is what tells you money moved.",[11,1017,1018,1019,1022,1023,1027],{},"That means handlers must be ",[82,1020,1021],{},"idempotent",". Stripe retries deliveries. If your handler grants access or cancels a subscription twice because it got called twice, you have a bug that only shows up under load. We've written in detail about ",[31,1024,1026],{"href":286,"rel":1025},[35],"a webhook where some failures must throw and some must never do"," — the distinction is the difference between a self-healing system and a support ticket.",[11,1029,1030,1031,1035,1036,1039],{},"Compliance lives here too. Encoding a ",[31,1032,1034],{"href":293,"rel":1033},[35],"German withdrawal-right waiver into the pay button"," via Stripe's ",[636,1037,1038],{},"consent_collection"," is not something a vibe prompt knows to do. It's compliance as code, and it's mandatory in the EU.",[20,1041,1043],{"id":1042},"agent-consistency-writing-conventions-that-survive-updates","Agent Consistency: Writing Conventions That Survive Updates",[11,1045,1046],{},"An agent cannot smell a codebase. Give it three ways to fetch data and it adds a fourth — not because it's dumb, but because it has no reason to prefer yours. This is the failure mode behind \"anyone can code\": the agent drifts, and by month three you have five patterns for one job.",[11,1048,1049,1050,1052,1053,1057],{},"The fix is a contract. An ",[636,1051,638],{}," file documents one way to access data, handle secrets, and apply patches, so ",[31,1054,1056],{"href":60,"rel":1055},[35],"agent output stays consistent"," past the first session. Gemini's sprint-ahead style has no equivalent plan-and-confirm gate, which is fine for a demo and dangerous for a codebase you'll maintain for a year.",[20,1059,1061],{"id":1060},"vibe-coding-languages-frameworks-and-real-bugs","Vibe Coding Languages, Frameworks, and Real Bugs",[11,1063,1064,1065,1069],{},"Most vibe coding assumes one language — JavaScript or TypeScript — and one happy path. Production is messier. A serious SaaS often needs ",[31,1066,1068],{"href":175,"rel":1067},[35],"four languages from day one"," via i18n, where a single new locale string has to land in five places before the build stops complaining.",[11,1071,1072,1073,1077,1078,1083,1084,1087,1088,1093],{},"Real debugging stories make the point. We shipped a page that ",[31,1074,1076],{"href":277,"rel":1075},[35],"returned 200 from curl and 500 in Chrome"," — a JSON-LD hydration bug hiding in source order. Our blog once ",[31,1079,1082],{"href":1080,"rel":1081},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Four-blog-canonically-pointed-at-localhost",[35],"told Google its canonical URL was localhost:3000",". A ",[636,1085,1086],{},"@vercel\u002Fanalytics"," install ",[31,1089,1092],{"href":1090,"rel":1091},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fvercel-web-analytics-nuxt-4-analytics-package-breaks-typecheck",[35],"broke Nuxt typecheck"," through a peer-dependency conflict. None of these appear in a vibe-coding demo. All of them appear in a real project.",[20,1095,1097],{"id":1096},"typed-end-to-end-why-vibe-coding-needs-typescript-discipline","Typed End to End: Why Vibe Coding Needs TypeScript Discipline",[11,1099,1100,1101,1105],{},"Natural-language-to-code loves shortcuts, and the first shortcut is usually type safety. That's a false economy. TypeScript in ",[31,1102,1104],{"href":175,"rel":1103},[35],"strict mode"," catches bugs at compile time instead of in a customer's checkout. Pair it with Zod validation and a database schema treated as a single source of truth, and refactors stop being terrifying. Vibe code without types and you're signing up for refactoring hell the first time requirements change.",[20,1107,1109],{"id":1108},"deployment-speed-is-not-shipping-speed","Deployment Speed Is Not Shipping Speed",[11,1111,1112],{},"\"Deploy to Cloud Run in minutes\" is a genuine feature. But fast-to-first-deploy and safe-in-production pull in opposite directions. A template you clone hands you parts. A kit that adapts to your interview answers hands you a wired product — and, in BoiledPlate's case, delivers it through a GitHub invite with lifetime updates. The delivery mechanism is instant; the value is that the plumbing already agrees with itself.",[20,1114,1116],{"id":1115},"when-vibe-coding-makes-sense-and-when-it-doesnt","When Vibe Coding Makes Sense (And When It Doesn't)",[11,1118,1119],{},"Be honest about fit.",[11,1121,1122,1125,1126,1131],{},[82,1123,1124],{},"Reach for Gemini AI Studio"," for prototypes, internal tools, learning projects, and quick wins. It genuinely shines here, and Google's own ",[31,1127,1130],{"href":1128,"rel":1129},"https:\u002F\u002Fai.google.dev\u002F",[35],"vibe-coding documentation"," is a good starting point.",[11,1133,1134,1137],{},[82,1135,1136],{},"Reach for agent-driven plumbing"," the moment you have billing-critical, multi-tenant, or compliance-heavy requirements. The checklist is simple: does your app need webhooks, RLS, or signature verification? If yes, you've left vibe-coding territory.",[11,1139,1140],{},"The pragmatic middle is a hybrid — vibe code the UI, then apply deterministic patches to the dangerous parts.",[20,1142,1144],{"id":1143},"the-one-time-cost-vs-subscription-trap","The One-Time Cost vs. Subscription Trap",[11,1146,1147,1148,1153],{},"\"Free and fast\" often means \"expensive to maintain.\" Free vibe-coding access still leaves you owning recurring infrastructure and — worse — the ongoing cost of code nobody wrote a contract for. BoiledPlate Pro is €159 one-time with lifetime updates and no lock-in, and if you want to start free, ",[31,1149,1152],{"href":1150,"rel":1151},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Ffree-nuxt-supabase-saas-boilerplate",[35],"BoiledPlate Lite is MIT-licensed",". What you actually pay for isn't the stack — it's the agent-readable contracts, deterministic patches, and compliance encoded as code.",[20,1155,1157],{"id":1156},"the-future-of-vibe-coding-maturity-not-speed","The Future of Vibe Coding: Maturity, Not Speed",[11,1159,1160,1161,1163],{},"The trajectory is clear: from \"write code fast\" to \"write code safely.\" ",[636,1162,638],{},"-style contracts are becoming the norm, and deterministic patches are the bridge between a natural-language prompt and code you'd put in front of a paying customer. Speed got us the demo. Consistency gets us production.",[20,1165,1167],{"id":1166},"getting-started","Getting Started",[11,1169,1170,1171,1176],{},"Use Gemini when you're learning or experimenting. Use an agent-driven kit when you're shipping something with money, tenants, or regulators involved. If your vibe-coded app touches billing state, isolates user data, or verifies a webhook signature, the plumbing is your project — and it's worth reading ",[31,1172,1175],{"href":1173,"rel":1174},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-supabase-stripe-saas-boilerplate",[35],"what wiring a Nuxt, Supabase and Stripe SaaS actually demands"," before you promise a launch date.",{"title":360,"searchDepth":361,"depth":361,"links":1178},[1179,1180,1181,1182,1183,1184,1185,1186,1187,1188,1189,1190,1191,1192],{"id":904,"depth":364,"text":905},{"id":914,"depth":364,"text":915},{"id":927,"depth":364,"text":928},{"id":959,"depth":364,"text":960},{"id":984,"depth":364,"text":985},{"id":1006,"depth":364,"text":1007},{"id":1042,"depth":364,"text":1043},{"id":1060,"depth":364,"text":1061},{"id":1096,"depth":364,"text":1097},{"id":1108,"depth":364,"text":1109},{"id":1115,"depth":364,"text":1116},{"id":1143,"depth":364,"text":1144},{"id":1156,"depth":364,"text":1157},{"id":1166,"depth":364,"text":1167},"2026-07-17","Explore vibe coding with Google's Gemini: how natural language turns into working apps. Learn what's missing between impressive demos and production-ready systems.",{},"\u002Fblog\u002Fvibe-coding-gemini-production",{"title":896,"description":1194},"blog\u002Fvibe-coding-gemini-production",[1200,1201,1202,1203],"vibe-coding","gemini","ai-development","cloud-run","9t7yKExFOOtTP4gAd2PO34EvsBA731bM-sFnHMUa4E0",{"id":1206,"title":1207,"author":6,"body":1208,"category":6,"date":1533,"description":1534,"draft":380,"extension":381,"image":6,"meta":1535,"navigation":383,"path":1536,"seo":1537,"stem":1538,"tags":1539,"__hash__":1543},"blog\u002Fblog\u002Fandrej-karpathy-vibe-coding.md","Andrej Karpathy's Vibe Coding: The Rise and Fall",{"type":8,"value":1209,"toc":1517},[1210,1213,1217,1220,1223,1226,1229,1233,1246,1249,1252,1255,1259,1262,1265,1268,1272,1275,1287,1290,1297,1301,1304,1307,1310,1314,1320,1326,1332,1338,1344,1348,1356,1359,1362,1365,1369,1372,1375,1378,1382,1385,1388,1391,1395,1398,1405,1408,1412,1415,1461,1465,1468,1471,1475,1478,1481,1484,1488,1494,1500,1506],[11,1211,1212],{},"Andrej Karpathy dropped a tweet in February 2025 that renamed how a generation of developers talked about their work. \"Vibe coding,\" he called it — fully giving in to the vibes, embracing exponentials, forgetting the code even exists. Within a year the phrase was everywhere, then it curdled into a buzzword, and by February 2026 Karpathy himself had quietly moved on. This guide traces the whole arc: what vibe coding actually meant, where it breaks, and what serious builders do instead.",[501,1214,1216],{"id":1215},"what-is-vibe-coding","What is Vibe Coding?",[11,1218,1219],{},"Vibe coding is software development where you lean on a large language model to generate code and trust its output rather than reading every line. Karpathy's framing was deliberately loose: describe what you want, accept the diff, run it, and if it works, keep going.",[11,1221,1222],{},"The core philosophy is about embracing exponential capability. Models improve fast, so why fight them with perfectionism? You prompt, you iterate, you ship.",[11,1224,1225],{},"This is a genuine break from structured, methodical coding, where every function is reasoned about and every architectural decision is deliberate. Vibe coding says: let the model hold the details, you hold the intent.",[11,1227,1228],{},"The mindset shift is real. You stop being the author and start being the director. That works beautifully — right up until it doesn't.",[501,1230,1232],{"id":1231},"the-origins-karpathys-vision","The Origins: Karpathy's Vision",[11,1234,1235,1236,1240,1241,1245],{},"The ",[31,1237,1239],{"href":33,"rel":1238},[35],"original post"," landed in early 2025 and spread within days. ",[31,1242,1244],{"href":404,"rel":1243},[35],"Wikipedia"," now credits Karpathy with coining the term.",[11,1247,1248],{},"What he actually meant was narrower than how it was received. His examples were throwaway projects — weekend apps, scripts, things where a bug just meant asking the model to fix it. The point was fun, not recklessness.",[11,1250,1251],{},"The misinterpretation came fast. \"Vibe coding\" got read as license to ship production software without understanding it. That is not what the phrase was built to carry.",[11,1253,1254],{},"Context matters. In early 2025, AI coding was good enough to feel magical and immature enough to fail silently. Vibes filled the gap between capability and reliability.",[501,1256,1258],{"id":1257},"how-vibe-coding-actually-works-in-practice","How Vibe Coding Actually Works in Practice",[11,1260,1261],{},"In practice, vibe coding is a rhythm: prompt, read the result loosely, run it, correct with another prompt. You stay in flow, and the LLM absorbs the tedium.",[11,1263,1264],{},"The skill is knowing when to override the vibe. If the output touches money, auth, or user data, you stop vibing and start reading. If it's UI scaffolding or a data transform, you let it ride.",[11,1266,1267],{},"Tools like Cursor and Claude made this possible, but the real enabler was architectural: choosing a stack and conventions the model already understands well. A model vibes better inside familiar terrain.",[501,1269,1271],{"id":1270},"vibe-coding-meets-production-reality","Vibe Coding Meets Production Reality",[11,1273,1274],{},"Vibes carry you through scaffolding. They collapse at the plumbing.",[11,1276,1277,1278,1281,1282,1286],{},"We learned this building ",[31,1279,437],{"href":175,"rel":1280},[35],", where the stack was the easy part and the wiring ate the weeks. As we argued in ",[31,1283,1285],{"href":259,"rel":1284},[35],"how to ship SaaS fast",", the framework picks itself — Stripe verification, row-level security, and idempotency are where launches actually stall.",[11,1288,1289],{},"You cannot vibe your way to a signature-verified webhook. Cryptographic correctness is binary. Full vibe coding fails at scale because the failures are silent: a user sees someone else's data, a subscription state drifts, a webhook fires twice.",[11,1291,1292,1293,1296],{},"What helps is structure. Building SaaS with agents requires contracts — an ",[31,1294,638],{"href":60,"rel":1295},[35]," file that documents one way to do data access and secrets, so the agent stays consistent instead of inventing a fourth pattern.",[501,1298,1300],{"id":1299},"the-karpathy-pivot-why-he-moved-on-february-2026","The Karpathy Pivot: Why He Moved On (February 2026)",[11,1302,1303],{},"By February 2026, Karpathy had publicly declared vibe coding outdated. His reasoning: LLMs got smart enough that \"vibes\" was no longer the right word for what good AI-assisted development looked like.",[11,1305,1306],{},"The landscape had matured. Models could follow explicit conventions, apply structured edits, and reason about architecture. The loose, forget-the-code-exists ethos felt incomplete against that.",[11,1308,1309],{},"His pivot signals something bigger: AI development grew up. The frontier moved from \"trust the model\" to \"constrain the model well.\" The industry got stuck arguing about the word \"vibe\" while the actual evolution was happening in tooling and contracts.",[501,1311,1313],{"id":1312},"five-different-approaches-to-vibe-coding","Five Different Approaches to Vibe Coding",[11,1315,1316,1319],{},[82,1317,1318],{},"Pure vibes."," Full trust, minimal oversight. Great for scripts and prototypes. Fails predictably for anything with real users.",[11,1321,1322,1325],{},[82,1323,1324],{},"Vibes with guardrails."," Prompting combined with deterministic patches and schema validation, so the model's output gets checked before it lands.",[11,1327,1328,1331],{},[82,1329,1330],{},"Vibe coding for architecture."," Use agents to design systems and explore options, then let humans wire the sensitive plumbing by hand.",[11,1333,1334,1337],{},[82,1335,1336],{},"Agent-native development."," Build around an AGENTS.md contract so agents produce consistent output across months, not just across a single session.",[11,1339,1340,1343],{},[82,1341,1342],{},"Post-vibe coding."," Structured prompting, explicit contracts, deterministic outputs. This is the direction Karpathy's pivot points toward.",[501,1345,1347],{"id":1346},"vibe-coding-vs-deterministic-coding","Vibe Coding vs. Deterministic Coding",[11,1349,1350,1351,1355],{},"The problem with vibes alone is drift. An agent given three ways to fetch data will ",[31,1352,1354],{"href":60,"rel":1353},[35],"cheerfully add a fourth",", because it has no reason to prefer yours.",[11,1357,1358],{},"Drift costs rework. Every time LLM output diverges from your conventions, someone has to notice, refactor, and re-explain — often the agent itself, badly.",[11,1360,1361],{},"Deterministic patches and semantic contracts prevent this decay. Instead of hoping the model matches your style, you encode the style as rules it must follow.",[11,1363,1364],{},"The concrete cases make it obvious: webhook idempotency, RLS policies, and multi-language i18n are all places where \"close enough\" is a bug. There are five places a new locale string has to land before the build stops complaining, and vibes will find four of them.",[501,1366,1368],{"id":1367},"the-business-case-vibe-coding-in-startup-context","The Business Case: Vibe Coding in Startup Context",[11,1370,1371],{},"The speed gains from vibes are real and measurable — for the first mile. Scaffolding a landing page, a dashboard shell, a data model happens in minutes now.",[11,1373,1374],{},"Then the curve inverts. The weeks you saved on scaffolding get spent debugging the plumbing vibes couldn't handle. Founders who track this honestly land on the same rule: vibes for the MVP, structure for scale.",[11,1376,1377],{},"Karpathy's 2025 enthusiasm faded by 2026 partly through survivorship filtering. The demos that went viral were the ones that worked. The vibe-coded projects that quietly died in production billing bugs didn't trend.",[501,1379,1381],{"id":1380},"is-vibe-coding-dead","Is Vibe Coding Dead?",[11,1383,1384],{},"The buzzword trap killed the term more than the technique. Once every tool marketed itself as \"vibe coding,\" the phrase meant nothing.",[11,1386,1387],{},"What survived is the useful core: describe intent, let the model do the mechanical work, iterate fast.",[11,1389,1390],{},"What changed is the emphasis. LLMs are smarter, so the need for \"vibes\" shifted to \"conventions.\" The real skill now is judgment — knowing when to trust the agent and when to enforce determinism.",[501,1392,1394],{"id":1393},"the-anti-hype-take-what-developers-actually-need","The Anti-Hype Take: What Developers Actually Need",[11,1396,1397],{},"Here's the uncomfortable read: vibe coding solved the wrong problem. It framed the challenge as attitude — loosen up, trust the model — when the challenge was actually tooling.",[11,1399,1400,1401,74],{},"The real innovation was never vibes. It was agent-readable contracts: AGENTS.md, structured prompts, deterministic provisioning. Every starter that ships the stack misses the point; ",[31,1402,1404],{"href":348,"rel":1403},[35],"the stack was never the hard part",[11,1406,1407],{},"Starter kits with strong conventions beat pure vibes because they give the agent a floor. Building SaaS the way Karpathy now implies means structure plus AI, not vibes plus hope.",[501,1409,1411],{"id":1410},"technical-specifics-where-vibes-fail","Technical Specifics: Where Vibes Fail",[11,1413,1414],{},"Some things simply do not bend to attitude:",[76,1416,1417,1428,1434,1440,1451],{},[79,1418,1419,1422,1423,1427],{},[82,1420,1421],{},"Webhook signature verification."," You cannot vibe cryptographic correctness. See our writeup on treating ",[31,1424,1426],{"href":286,"rel":1425},[35],"the GitHub invite as the product",", where some failures must throw and some must never.",[79,1429,1430,1433],{},[82,1431,1432],{},"Row-level security."," RLS is explicit, not emergent. A missing policy is a data breach, not a rough edge.",[79,1435,1436,1439],{},[82,1437,1438],{},"Idempotent transactions."," The two-generals problem doesn't care how confident your prompt sounded.",[79,1441,1442,1445,1446,1450],{},[82,1443,1444],{},"Consent flows."," ",[31,1447,1449],{"href":293,"rel":1448},[35],"German withdrawal law"," has specific requirements you encode into the pay button, or you don't sell legally.",[79,1452,1453,1445,1456,1460],{},[82,1454,1455],{},"Billing state.",[31,1457,1459],{"href":88,"rel":1458},[35],"Stripe webhooks are the source of truth",", not the optimistic client-side success page.",[501,1462,1464],{"id":1463},"tools-and-patterns-for-post-vibe-coding","Tools and Patterns for Post-Vibe Coding",[11,1466,1467],{},"This is exactly what BoiledPlate encodes: the lessons of vibe coding turned into structure. Instead of vibing through setup, an agent-driven interview provisions Stripe products and webhooks, a Supabase database with RLS, and Google sign-in in one session — deterministically.",[11,1469,1470],{},"The AGENTS.md contract is the evolution of vibes into something a machine can read and honor. And semantic, agent-readable release notes let agents apply updates consistently instead of guessing.",[501,1472,1474],{"id":1473},"lessons-for-the-next-wave-of-ai-coding","Lessons for the Next Wave of AI Coding",[11,1476,1477],{},"Vibe coding was a necessary phase, not the destination. It taught developers that intent-first workflows are faster — and that unstructured trust doesn't survive production.",[11,1479,1480],{},"Karpathy's pivot tells us where things head: verification over trust, contracts over vibes. The skills that will matter are prompt engineering, contract design, and knowing what to check.",[11,1482,1483],{},"The best AI-native code, it turns out, looks less like vibes and more like highly structured conventions a model can follow without drifting.",[501,1485,1487],{"id":1486},"faq-common-misconceptions-about-vibe-coding","FAQ: Common Misconceptions About Vibe Coding",[11,1489,1490,1493],{},[82,1491,1492],{},"Does vibe coding mean no testing?"," No. The durable version is vibes plus verification — generate loosely, validate strictly.",[11,1495,1496,1499],{},[82,1497,1498],{},"Is Karpathy saying not to use LLMs?"," The opposite. Use them heavily, but with determinism and explicit constraints.",[11,1501,1502,1505],{},[82,1503,1504],{},"Can I ship production SaaS on vibes alone?"," Not sustainably. The plumbing — billing, security, compliance — demands structure.",[11,1507,1508,1511,1512,1516],{},[82,1509,1510],{},"What's the successor to vibe coding?"," Agent-native development built on contracts. Start from ",[31,1513,1515],{"href":1150,"rel":1514},[35],"a boilerplate designed for agents"," rather than vibing the wiring yourself.",{"title":360,"searchDepth":361,"depth":361,"links":1518},[1519,1520,1521,1522,1523,1524,1525,1526,1527,1528,1529,1530,1531,1532],{"id":1215,"depth":361,"text":1216},{"id":1231,"depth":361,"text":1232},{"id":1257,"depth":361,"text":1258},{"id":1270,"depth":361,"text":1271},{"id":1299,"depth":361,"text":1300},{"id":1312,"depth":361,"text":1313},{"id":1346,"depth":361,"text":1347},{"id":1367,"depth":361,"text":1368},{"id":1380,"depth":361,"text":1381},{"id":1393,"depth":361,"text":1394},{"id":1410,"depth":361,"text":1411},{"id":1463,"depth":361,"text":1464},{"id":1473,"depth":361,"text":1474},{"id":1486,"depth":361,"text":1487},"2026-07-16","Explore vibe coding, Andrej Karpathy's controversial approach to AI-assisted development. Understand what it means, where it breaks, and serious alternatives.",{},"\u002Fblog\u002Fandrej-karpathy-vibe-coding",{"title":1207,"description":1534},"blog\u002Fandrej-karpathy-vibe-coding",[388,1540,1541,1542],"andrej karpathy","ai development","software engineering","SACUbmvSS-AaQ5e5rFj_7Tzsc3NC1Ldhz-Gf4C2uvSs",1784422315617]