Stop Vibe Coding: Start Spec-Driven Development, with John Capobianco

What comes after vibe coding?

In this episode, John Capobianco joins us to explore Spec-Driven Development and how tools like GitHub Spec Kit and Claude Code can bring structure, requirements, testing, and repeatability to AI-assisted software development.

Instead of simply prompting an LLM to “build me an app” and hoping for the best, we work through a structured development process:

Constitution → Specify → Clarify → Plan → Tasks → Implement

We build a working subnetting learning game from scratch, without writing the application code ourselves. Along the way, Spec Kit creates requirements, user stories, acceptance criteria, implementation plans, tests, and the artifacts needed to turn an idea into working software.

We also dig into some bigger questions:

* What separates vibe coding from actual software development? * Can network engineers build useful software without becoming traditional developers? * How does Spec-Driven Development improve AI-generated code? * Can AI test and validate the code it generates? * How much do you actually need to understand the underlying code? * What does all of this mean for the future of network engineering?

If you're experimenting with Claude Code, AI coding, network automation, GitHub Spec Kit, or vibe coding, this episode shows what happens when you stop relying on prompts alone and start giving AI a real development process.

Subscribe for more content from The Art of Network Engineering.

Links: * John Capobianco: https://artofnetworkengineering.com/guests/john-capobianco * Eric Chou: https://artofnetworkengineering.com/guests/eric-chou * Spec Kit: https://github.com/github/spec-kit * NAF / AutoCon: https://networkautomation.forum/ * AONE: https://artofnetworkengineering.com/

This episode is sponsored by Meter. Go to https://meter.com/aone to book a demo now!

#NetworkEngineering #NetworkAutomation #SpecDrivenDevelopment #VibeCoding #ClaudeCode #GitHub #AI #SoftwareDevelopment