Outgrowing the Vibe Code

john crider

You started by tossing prompts at an AI and hoping the app held together. It worked... until it didn't. Outgrowing the Vibe Code is the show about what comes next. Each episode, two builders dig into the messy, fascinating journey from haphazard "vibe coding" to real, enterprise-grade systems that write code for you. We get hands-on with the stuff that makes it work — harnesses, spec-driven development (SDD), and agent loops — without the jargon or the hype. Whether you're still winging it or wiring up your first self-writing pipeline, pull up a chair. It's fun, it's casual, and it's the con

Tập

  1. 3 ngày trước

    The Agent Isn't the Hard Part

    Every time the agent does something dumb, there's a comforting little prayer: the next model will fix it. Ada and Boris open Chapter 3 by showing why that's backwards — AI coding has compressed three eras into three years (prompt engineering, then context engineering, then harness engineering), and a frontier model that scores 90%+ in a clean test still falls apart on real work. Not because it can't reason, but because it's a brilliant new hire dropped in with no onboarding, no tests, no guardrails. With three receipts — LangChain jumping 13.7 points by changing only the harness, Vercel going 80% to 100% by cutting fifteen tools down to two, and the APEX-Agents benchmark exposing a 24% real-world pass rate from orchestration failures — they land the pattern: once a model crosses the capability threshold, more intelligence has diminishing returns while every harness improvement compounds across every future session. From Chapter 3 of *Harness Engineering for Vibe Coders* by J.M. Crider — go deeper at hamiltonroadagility.com/vibe

    12 phút

  2. 5 ngày trước

    When You Can't Trust "Done"

    Your agent says "done" with total confidence — but can you trust it? Ada and Boris close out the failure-modes chapter with the two trust failures: the fixation loop, where the agent fixes one thing and breaks another round after round because nothing checks the whole picture, and confidence without verification, where every answer arrives equally certain even when the agent is flat-out wrong (and will happily agree with you to boot). Then they step back to the big payoff: all eight failures across the chapter are one root cause — the agent isn't broken, it's unsupported, like a brilliant new hire dropped into an empty room. The fix clusters into four kinds of infrastructure — documentation, architecture, verification, and context management — the four pillars every harness is built from. From Chapter 2 of *Harness Engineering for Vibe Coders* by J.M. Crider — go deeper at hamiltonroadagility.com/vibe

    11 phút

  3. 18 thg 6

    When the Code Rots

    Your agent's code can look perfect and still rot from the inside. Ada and Boris walk through the three ways it happens: the copy-paste explosion — the agent reinventing the same little utility instead of reusing yours, at roughly eight times the duplication rate of human-written code; phantom completions — features it cheerfully calls "done" that were never actually run; and architecture erosion — a clean, layered design quietly collapsing as the agent takes one shortcut after another. The through-line: every one is invisible at the level of a single change and only shows up when you step back and look at the whole project. From Chapter 2 of *Harness Engineering for Vibe Coders* by J.M. Crider — go deeper at hamiltonroadagility.com/vibe

    11 phút

  4. 16 thg 6

    When the Agent Forgets

    Your coding agent keeps making confident mistakes — calling a function with the wrong arguments, drifting away from your naming conventions file by file, and starting every session like it's never met your project. In this episode, Ada and Boris trace all three back to a single root cause: the agent can't remember. They unpack context overflow (the agent filling a partial view with plausible-but-wrong guesses), convention drift (re-inferring your rules from whatever code is in front of it, until the inconsistency becomes the rule), and the blank-slate problem — a stateless tool that forgets everything when the session ends, multiplying every other failure mode. From Chapter 2 of *Harness Engineering for Vibe Coders* by J.M. Crider — go deeper at hamiltonroadagility.com/vibe

    13 phút

  5. 13 thg 6

    Why Trying Harder Fails and the Name for the Fix

    Last episode named the wall — this time, why your instincts for getting past it all fail. Ada and Boris dig into why longer prompts, fresh sessions, and micromanaging the AI don't work: each one treats a structural problem like a communication problem. The real story is that the agent isn't broken — it's a stateless predictor missing the infrastructure *around* it (memory, verification, architecture), and output quality is set by the environment, not the model. That discipline has a name — harness engineering — and it's what the rest of the show is about. From Chapter 1 of *Harness Engineering for Vibe Coders* by J.M. Crider — go deeper at hamiltonroadagility.com/vibe

    13 phút

  6. 12 thg 6

    The Honeymoon and the Wall

    You build an app with AI over a weekend and it feels like magic — then three weeks later it's fighting you at midnight. That's *the wall*, and almost everyone hits it. In our first full episode, Ada and Boris break down why AI-built projects feel so good at first, the four ways they start to crack as they grow — repetition, contradiction, phantom completion, and cascade failure — and the unsettling "perception gap" that hides the wall while you're standing right at it. From Chapter 1 of *Harness Engineering for Vibe Coders* by J.M. Crider — go deeper at hamiltonroadagility.com/vibe

    13 phút

  7. Đoạn giới thiệu phim của Phần 1

    Who This Is For

    Is this show for you? If you've built something with AI and watched it slowly fall apart, if you're curious about AI-built software but you're not a programmer, or if you're a developer whose job is shifting from writing code to directing it — yes. Here's what *Outgrowing the Vibe Code* means, who gets the most out of it, and our promise: one usable idea per episode, no jargon left unexplained, all in under 15 minutes. Book: *Harness Engineering for Vibe Coders* by J.M. Crider — hamiltonroadagility.com/vibe

    3 phút

  8. Đoạn giới thiệu phim của Phần 1

    How This Show Is Made

    Before we teach anything, one honest conversation. *Outgrowing the Vibe Code* is hosted by two AI voices — Ada and Boris — working from AI-assisted scripts, and in this opener we tell you exactly how it's made, and why a human was the architect of every step: holding the vision, designing the system, and correcting course when things drifted. It's the book's own method — harness engineering — demonstrated on itself. Plus a quick look at the journey ahead. New here? Start with this. Book: *Harness Engineering for Vibe Coders* by J.M. Crider — hamiltonroadagility.com/vibe

    5 phút

Trailers

Giới Thiệu

You started by tossing prompts at an AI and hoping the app held together. It worked... until it didn't. Outgrowing the Vibe Code is the show about what comes next. Each episode, two builders dig into the messy, fascinating journey from haphazard "vibe coding" to real, enterprise-grade systems that write code for you. We get hands-on with the stuff that makes it work — harnesses, spec-driven development (SDD), and agent loops — without the jargon or the hype. Whether you're still winging it or wiring up your first self-writing pipeline, pull up a chair. It's fun, it's casual, and it's the con

Thông Tin

  • Nhà sáng tạo
    john crider
  • Năm hoạt động
    2 N
  • Tập
    8
  • Xếp hạng
    Sạch
  • Bản quyền
    © john crider
  • Trang web chương trình
    Outgrowing the Vibe Code