# vibe-coding

After eight years of hesitation, Lalit Maganti spent roughly 250 hours over three months building syntaqlite with AI coding agents. He reports on a discarded month of vibe-coding, prompt addiction, lost codebase context, and the boundary between AI-accelerated implementation and human-led design.

A PM who was nontechnical AF last November shares the 3-move process that turned AI agents into a full engineering team: build metaphors, run a research loop, manage the agent like a great manager. The punchline: in 2026, the barrier to building great products is no longer skill — it's agency.

Karpathy found that vibe coding makes writing code a breeze, but deployment is pure hell. His exchange with Stripe CEO Patrick Collison reveals the next battleground: the entire DevOps lifecycle must become code before AI agents can truly take over.

Karpathy's MenuGen journey shows the hard part of vibe coding was not writing code, but assembling Vercel, Clerk, Stripe, OpenAI, and other services into a product. His takeaway: DevOps must become code before agents can really ship.

Berryxia uses Dense vs MoE to explain why Codex shines at bug fixes, refactors, and long-running engineering while Claude wins vibe coders. The real split is broader: training philosophy, product design, and precise delegation versus 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 Vibe Coding's adoption driver is not just faster code, but removing the telephone game between domain experts and implementation. The catch: unclear intent still produces the wrong thing at warp speed.

Karpathy says coding agents started working in December 2025 as a hard discontinuity. He built a DGX Spark video analysis dashboard in 30 minutes from one English sentence. Programming is becoming agent direction, not typing.

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.

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'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.

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 months of effort into seconds. The rush is not it works, but I cannot believe it works. The author dissects dopamine, consumption disguised as creation, and the vertigo of infinite possibilities.

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.

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