『Vibe Coding to Agentic Engineering: When Everyone Can Build, What Matters Is What You Build』のカバーアート

Vibe Coding to Agentic Engineering: When Everyone Can Build, What Matters Is What You Build

Vibe Coding to Agentic Engineering: When Everyone Can Build, What Matters Is What You Build

無料で聴く

ポッドキャストの詳細を見る

概要

 The Emergent Podcast — Episode 9Vibe Coding to Agentic Engineering: When Everyone Can Build, What Matters Is What You Build"AI is now awake. And it's a big contrast to even two, three months ago." — Nick BaguleyListen on: Apple Podcasts · Spotify · YouTube · RSSEpisode Duration: ~1 hr 40 min | Published: 2026 | Season 1, Episode 9🎙️ Episode SummaryOne tweet changed a word. The word changed an industry. The industry is changing what it means to build.In February 2025, Andrej Karpathy — co-founder of OpenAI and former head of AI at Tesla — published a single post coining the term "vibe coding": describe what you want in plain English, accept all AI-generated code without reading the diffs, and just… vibe. Twelve months later, it became the Collins Dictionary Word of the Year, 92% of U.S. developers use AI coding tools daily, 41% of all code is AI-generated — and Karpathy himself has already declared it passé, rebranding the practice as "agentic engineering."In Episode 9, Justin Harnish and Nick Baguley dig into what really happened in that extraordinary year. Both hosts share their personal workflows and real projects — including Justin's intermittent fasting app, his vision of a personal "digital brain" with AI-queryable embeddings, and Nick's AI-native marketplace designed for both human and agent users. They navigate the empirical gut-punch of the METR study(developers are actually 19% slower on mature codebases using AI), the existential labor market questions (traditional programmer roles down 27.5% since ChatGPT's launch), and the philosophical territory that has been the Emergent Podcast's throughline since Episode 1: when code becomes a commodity, what becomes scarce?Their answer: responsible agency — the judgment to decide what should be built, for whom, and with what values. That, they argue, is the skill that neither automation nor benchmarks can yet replicate.📚 Resources & Reading ListEvery link mentioned or referenced in this episode. Organized by theme for your exploration.🔑 The Origin & The Debate (Required Reading)Andrej Karpathy's Original "Vibe Coding" Tweet (Feb 2, 2025)The tweet that launched the year. Karpathy describes accepting all AI code without reading diffs, pasting errors back without comment, and letting the codebase grow beyond comprehension. Note the caveat he included that industry largely ignored: "not too bad for throwaway weekend projects."Karpathy's 2025 LLM Year in Review — bearblog.devHis retrospective on vibe coding's arc from shower-thought tweet to Collins Dictionary Word of the Year. Key insight: "Code is suddenly free, ephemeral, malleable, discardable after single use." He also identifies Claude Code as the first convincing LLM agent.Karpathy on "Agentic Engineering" (Feb 2026) — The New StackOne year after coining vibe coding, Karpathy declares it passé. His new frame — agentic engineering— emphasizes that professionals orchestrate AI agents 99% of the time, with zero compromise on software quality. The rebrand is the narrative bookend of this episode.Simon Willison — "Not All AI-Assisted Programming Is Vibe Coding" (Mar 2025) — simonwillison.netThe essential distinction: "If an LLM wrote every line of your code, but you've reviewed, tested, and understood it all, that's not vibe coding — that's using an LLM as a very fast typist." Also contains Willison's generous vision: "Everyone deserves the ability to automate tedious tasks."METR Study: AI Makes Experienced Devs 19% Slower (Jul 2025) — metr.orgThe empirical gut-punch of the episode. 16 experienced open-source developers, 246 real-world tasks. They believed AI made them 20% faster; they were actually 19% slower on their own mature codebases. Full paper: arxiv.org/abs/2507.09089Vibe Coding — WikipediaSurprisingly rigorous. Tracks the full timeline, Lovable's 170 vulnerable apps, CodeRabbit's finding that AI code has 1.7× more major issues, Y Combinator stats (25% of W25 startups are 95% AI-coded), and the "vibe coding hangover" reported by Fast Company.📖 Supplemental: The Deeper CutsScott H. Young — "Is Vibe Coding the Future of Skilled Work?"The variance argument: vibe coding may make software both much worse and much better simultaneously. Also argues that conceptual knowledge becomes more, not less, important when AI writes the code. A crucial counterweight to pure optimism.IBM — "What Is Vibe Coding?"Enterprise-oriented overview. Useful on the agile alignment: vibe coding fits fast-prototyping and iterative development. Contains the key qualifier Nick and Justin both echo: "AI generates code, but creativity, goal alignment, and out-of-the-box thinking remain uniquely human."Google Cloud — "Vibe Coding Explained: Tools and Guides"Practical tool comparison from Google's perspective — AI Studio, Firebase Studio, Gemini Code Assist. Useful for understanding which tool fits which use case.Software Engineering Job Market Outlook for 2026 — Final ...
まだレビューはありません