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

2026-06-09 · Source: GOTO Conferences · Field: Technology & Digital — Software Development & Engineering, Artificial Intelligence & Machine Learning · Depth: Intermediate, extended

Summary

Derek Bingham's YOW! 2025 talk, "404 – Developer Not Found: The Continuing Developer Evolution," explores how AI is disrupting software development. Bingham recounts building a functional Pac-Man/Snake game with his 12-year-old using an agentic coding assistant and a few prompts, demonstrating AI's capabilities. He contrasts this with "vibe coding" pitfalls, where AI-generated code can be extensive but non-functional. The presentation addresses developer anxieties, particularly for juniors, regarding AI replacement. Bingham traces tool evolution from VI to modern AI-assisted systems, emphasizing the rapid advancements over the last 18 months. He introduces "context engineering" as a critical skill, detailing the "context curve" and offering "context management 101" rules like ruthless chat management, chunking, and monitoring context windows. He debunks myths that AI will replace developers, citing the Dunning-Kruger effect and Jevons paradox, and that AI code is inferior, advocating for Spec Driven Development (SDD) to ensure quality.

Key takeaway

For software engineers adapting to AI-assisted development, you must shift from traditional coding to "context engineering" and structured interaction. Focus on defining clear requirements and architecture for agentic tools, then rigorously review generated code. Embrace Spec Driven Development (SDD) to manage context windows effectively and ensure quality, recognizing that continuous learning and ethical considerations are paramount as tools rapidly evolve. This approach will enable you to remain a disruptor, not merely a disrupted.

Key insights

The developer role is evolving, requiring new skills in context engineering and structured AI interaction to harness agentic coding assistants effectively.

Principles

• AI agents are only as good as the context provided.
• Increased efficiency from AI tools can lead to greater demand for developers (Jevons paradox).
• Continuous review and iteration are crucial for AI-generated code.

Method

Spec Driven Development (SDD) involves defining clear requirements, architectural decisions, and tasks iteratively with an agent, reviewing at each stage before execution to manage context and ensure quality.

In practice

• Ruthlessly manage chat windows to reset context.
• Use chunking for tasks; avoid "boiling the ocean."
• Monitor agent's context window size.

Topics

• AI-Assisted Coding
• Context Engineering
• Spec Driven Development
• Agentic Systems
• Developer Evolution
• Software Engineering Ethics

Best for: Software Engineer, AI Engineer, Consultant

Related on AIssential

• New course! Spec-Driven Development — Spec-driven development uses detailed specifications to guide AI agents, improving code quality and managing developer cognitive load.
• Context Is the New Code — Patrick Debois, Tessl — Effective AI agent performance hinges on meticulously engineered context, necessitating a dedicated Context Development Life Cycle.
• Top 10 Vibe Coding AI Tools Every Developer Should Use In 2026 — Vibe coding transforms developers into architects, using AI agents for intent-based programming and full-stack application deployment.
• Steve Yegge Wants You to Stop Looking at Your Code — AI agents will transform coding into orchestration, shifting human roles to managing complex problems and leveraging taste.
• How I code with agents, without being 'technical' — AI agents enable non-technical users to build complex software by abstracting traditional coding into a guided, iterative process.
• Spec-Driven Development Turns the Chaos of Vibe Coding Into Structured Delivery — Spec-Driven Development (SDD) resolves "Vibe Coding" bottlenecks by prioritizing formal specifications over ad-hoc AI prompting.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by GOTO Conferences.