Spec driven development

How to Kill the Code Review — Ankit Jain, Aviator

How to Kill the Code Review — Ankit Jain, Aviator

Ankit Jain argues that traditional line-by-line code review is defunct, with AI reviewing code that humans no longer read. He asserts that code review's vital, often overlooked, purpose is 'alignment'—knowledge sharing, mentorship, and architectural feedback—which current AI-driven workflows fail to capture. His proposal involves capturing user-AI interaction prompts as acceptance criteria, generating test plans with an 'AI Slop Registry' (codified recurring review comments), and verifying changes against live previews. The new review surface becomes the 'intent and evidence' rather than the code diff, preserving collaboration and ensuring semantic accuracy.

What Is RAD? Why It Matters in the Age of AI Coding

What Is RAD? Why It Matters in the Age of AI Coding

This video explores how James Martin's 1991 Rapid Application Development (RAD) methodology, with its emphasis on rapid prototyping, iterative development, and user feedback, offers a robust framework for contemporary AI coding and "vibe coding" workflows. It highlights how AI agents accelerate prototyping but introduces new challenges regarding production readiness and security. The solution proposed is spec-driven development, where human expertise formalizes requirements and verifies AI-generated code based on insights gained from early prototypes, ensuring quality and mitigating risks.

Using Spec-Driven Development for Production Workflows - Erik Hanchett, AWS

Using Spec-Driven Development for Production Workflows - Erik Hanchett, AWS

Erik Hanchett discusses spec-driven development (SDD) as a structured approach to building complex software features with AI coding assistants. He explains how to guide AI "interns" through distinct phases of requirements, design, and implementation, emphasizing context management, the use of "skills," and the crucial role of the human in the loop for review. Hanchett highlights AWS's Kiro tool, which automates much of this process, and the Model Context Protocol (MCP) for integrating external data sources, offering a pathway to higher-quality code and more effective AI collaboration.

[404] – Developer Not Found: The Continuing Developer Evolution • Derek Bingham • YOW! 2025

[404] – Developer Not Found: The Continuing Developer Evolution • Derek Bingham • YOW! 2025

Derek Bingham explores the rapid evolution of developer tools with AI, from coding assistants to autonomous agents. He emphasizes the shift from prompt engineering to context engineering, introduces Spec-Driven Development (SDD) as a framework for quality AI-generated code, and dispels fears about AI replacing developers, arguing instead for increased demand and the necessity of new skills like ethical and systems thinking.

BDD, ADR, PRD, WTF: Capturing Decisions for Humans and AI Alike — Michal Cichra, Safe Intelligence

BDD, ADR, PRD, WTF: Capturing Decisions for Humans and AI Alike — Michal Cichra, Safe Intelligence

Michal Cichra from Safe Intelligence explains how to maintain consistency in AI-driven software development by capturing decisions and enforcing rules. He argues for reviving Behavior-Driven Development (BDD) with Cucumber to close the loop left by spec-driven development. The core idea is to enforce architectural and product decisions (ADRs, PRDs) through an automated loop of git hooks and CI, ensuring both human and AI developers adhere to established standards.

The Creator of Superpowers: Why Real Agentic Engineering Beats Vibe Coding

The Creator of Superpowers: Why Real Agentic Engineering Beats Vibe Coding

Jesse Vincent, creator of the Claude plugin Superpowers, explains his methodology for agentic software development. He details a system of spec-driven development using brainstorming, planning, and execution skills that turn developers into managers of AI agents, emphasizing the importance of explaining the 'why' to LLMs and pressure-testing skills to prevent rationalization.