[FULL WORKSHOP] AI Coding For Real Engineers - Matt Pocock, AI Hero (@mattpocockuk )
TL;DR
Matt Pocock demonstrates how traditional software engineering principles apply to AI coding, teaching engineers to manage LLM limitations through "smart zones," avoid "specs-to-code" traps, and use structured interrogation techniques to achieve true alignment with AI agents.
🧠 LLM Constraints & Context Windows 3 insights
Smart Zone vs. Dumb Zone Dynamics
LLMs perform optimally in early context but degrade significantly after approximately 100k tokens due to strained attention relationships.
Quadratic Scaling Strains Attention Mechanisms
Adding tokens increases attention relationships quadratically, causing inevitable performance degradation regardless of total context window capacity.
Size All Tasks to Fit Smart Zones
Break large projects into discrete chunks that complete within the high-performance window before context quality deteriorates.
🔄 Session Architecture & State Management 3 insights
LLMs Reset to Base Like Memento
Clearing context provides predictable reset behavior superior to compacting, which creates inconsistent historical sediment.
Sessions Follow Four Distinct Phases
Every interaction progresses through minimal system prompt, exploration, implementation, and testing/validation stages.
Delegate Exploration to Isolated Sub-Agents
Offload research to child agents that report summaries back, preserving the parent agent's token budget for critical implementation work.
🤝 Effective Collaboration Patterns 3 insights
Reject Vibe Coding and Specs-to-Code
Engineers must directly understand and shape code rather than iterating only on specifications while ignoring implementation details.
Grill Me Protocol Establishes Shared Understanding
Relentlessly interrogate the AI about every plan aspect to align on design concept before writing any implementation code.
Ralph Wiggum Means Iterative Small Changes
Specify the end state and loop through minimal incremental changes rather than executing rigid multi-phase plans.
Bottom Line
Treat AI coding as structured engineering by aggressively managing context window limits through sub-agents and small tasks, while using structured interrogation to establish shared understanding before implementation.
More from AI Engineer
View all
Think You Can Build a Game with AI? Think Again! - Danielle An & David Hoe, Meta
Meta engineers Danielle An and David Hoe argue that while AI has democratized basic game creation, true differentiation requires human taste, cohesive aesthetics powered by key art anchoring, and innovative runtime LLMs that enable unscripted, dynamically personalized gameplay experiences previously impossible in traditional development.
Beyond the Harness: A Journey Towards Adaptative Engineering - Rajiv Chandegra, Annicha Labs
Rajiv Chandegra introduces 'adaptive engineering,' a paradigm shift from fixed AI harnesses (like Cursor or Claude Code) to dynamic, self-organizing systems that emerge during runtime, enabling AI to handle complex, real-world messes beyond deterministic software environments.
What if the harness mattered more than the model? - Aditya Bhargava, Etsy
Aditya Bhargava argues that sophisticated agent harnesses can compensate for weaker open-source models, enabling local AI to match proprietary performance while reducing vendor dependency.
Frontier results, on device - RL Nabors, Arize
Rachel Lee Neighbors introduces a framework for replacing expensive cloud-based frontier models with Small Language Models (SLMs) running on-device, demonstrating how a systematic 'prototype big, deploy small' approach using evaluation tools like Phoenix can cut inference costs to zero while maintaining 90% accuracy and enabling offline functionality.