# vibe-coding

Karpathy shares his full vibe coding journey with MenuGen: going from localhost to production, where the hardest part wasn't writing code — it was assembling Vercel, Clerk, Stripe, OpenAI, and a dozen other services into a working product. His takeaway: the entire DevOps lifecycle needs to become code before AI agents can truly ship for us.

Berryxia uses Dense vs MoE to explain something many developers already feel: Codex often shines in bug fixing, refactors, and long-running engineering tasks, while Claude keeps winning over vibe coders. That framing captures part of the truth, but the real split is bigger than architecture — it includes training philosophy, product design, and whether you treat coding as precise delegation or interactive creation.

Paweł Huryn proposes the Vibe Engineering framework: instead of accepting raw AI output, use Context Engineering, Intent Engineering, and Sub-agent orchestration to upgrade AI coding from 'lucky demos' to 'reliable products'.

Simon Willison used Claude Opus 4.6 and GPT-5.4 to vibe code two macOS menu bar apps — one for network traffic, one for GPU stats. The entire SwiftUI app fits in a single file, no Xcode needed. But he's the first to admit: he has no idea if the numbers are accurate.

Google AI dropped a week's worth of announcements in a single tweet — full-stack vibe coding in AI Studio, an AI-native design canvas called Stitch, major Gemini API upgrades, and a free hackathon platform on Kaggle.

SemiAnalysis argues that Vibe Coding's real adoption driver isn't just faster code — it's eliminating the long telephone game between domain experts and implementation. But if you don't know what you want, the LLM will happily build the wrong thing at warp speed, and production still needs real engineers.

Karpathy says coding agents started working in December 2025 — not gradually, but as a hard discontinuity. He built a full DGX Spark video analysis dashboard in 30 minutes with a single English sentence. Programming is becoming unrecognizable: you're not typing code anymore, you're directing AI agents in English. Peak leverage = agentic engineering.

Simon Willison tried Claude Code Remote Control and Cowork Scheduled Tasks — two Anthropic features that overlap with OpenClaw, both requiring your computer to stay on. Plus: vibe-coding a SwiftUI presentation app in 45 minutes with Tailscale phone remote control.

Karpathy's viral SF AI Startup School talk: software is entering the 3.0 era (English = programming language), LLMs are the new OS but we're in the 1960s. He introduces the 'autonomy slider' and 'Iron Man suit' frameworks, warning that agents are a decade-long journey, not a year.

Postlight's former CEO Paul Ford wrote in the NYT: projects he used to quote at $350K now take a weekend with Claude Code at $200/mo. Plus Andrew Ng's 'X Engineer' vision for the future of software jobs.

Karpathy used Claude Code to build a custom dashboard in 1 hr, reverse-engineering a treadmill API. He believes AI-native sensors & LLMs will enable highly custom, ephemeral apps, rendering the App Store model obsolete. The ultimate goal: 1-min app creation.

Vibe Coding is refined sugar for creation — compressing an experience that used to take months of effort into a few seconds. What gives you the rush isn't 'it works,' it's 'I can't believe it actually works.' The author dissects Vibe Coding addiction through dopamine mechanics, consumption disguised as creation, and the vertigo of infinite possibilities.

Cursor CEO claimed they built a browser from scratch using GPT-5.2, but developers discovered it was just stitching together existing open source components

ADPList founder Felix Lee wrote a Claude Code guide for designers, promoting 'Vibe Coding'. As a Claude Code power user, I analyze what this means for engineers and tech leads: designers' description skills are actually an advantage, but there's still a gap between vibe code and production code.