Matt Pocock on AI Skills, Strategic Coding, and Why Fundamentals Matter

⬅️ Back to Videos

🎥 Matt Pocock on AI Skills, Strategic Coding, and Why Fundamentals Matter

Gergely Orosz with Matt Pocock (Total TypeScript, AI Hero). Duration: 1 hr 37 min

Timestamps

  • 0:00 Intro
  • 5:48 From voice coach to developer
  • 18:39 Building Total TypeScript
  • 30:32 Building reusable skills for agents
  • 40:46 The smart zone vs the dumb zone
  • 45:02 The wayfinder skill
  • 50:54 Leading words
  • 1:01:10 Learning the fundamentals
  • 1:12:36 Planning vs course-correcting
  • 1:18:13 TDD and agents
  • 1:31:07 Gardeners and great engineers

Pocock spent six years as a voice coach before teaching himself to code. Now his skills repo is one of the most starred on GitHub, and his argument is simple. The old programming books work better on agents than most new prompting tricks.

  1. The grill-me skill just interviews you, relentlessly. Pocock credits the idea to Thariq Shihipar at Anthropic. The skill itself is tiny. It tells the agent to keep asking questions before writing code, and the result feels like a senior engineer in the room.
  2. Orosz got grilled for 35 questions over one simple API endpoint. Auth scheme, rate limits, scope, everything. He found it annoying and excellent at once. I liked his line that it had been years since a design discussion forced him to think that hard.
  3. Pocock says every agent has a communication gap with you. It cannot read your values, so a bare build-this prompt produces misaligned code. Grill-me fixes that early by settling what is in scope and what matters before anything gets written.
  4. Keep agents inside their smart zone. Pocock borrows the term from Dex Horthy. Past roughly 150,000 tokens the model holds too many voices at once and starts losing connections. His answer is to split big work across sessions instead of stuffing one window.
  5. His pipeline is grill, then spec, then tickets. The grilling session becomes a spec, the spec breaks into one ticket per session, and an implement loop works through 30 or 40 tickets. He plans during the day shift and lets agents run the night shift while he sleeps.
  6. Wayfinder handles jobs too big to plan in one sitting. It keeps a map with a fog of war, and each grilling, prototype, or research ticket opens more of the map. Pocock says he has run maps with 50 to 100 tickets, and he even used one to plan a garden office.
  7. The phrase tracer bullet changed his agent output. He lifted it from The Pragmatic Programmer. Instead of building the database layer, then the app layer, then the UI, the agent builds one working vertical slice first. The model started repeating the phrase back in its own reasoning traces.
  8. He calls these repeats leading words. Another favorite is ubiquitous language from Domain-Driven Design. He builds the domain terms with the agent, like naming a ghost lesson cascade a materialization cascade, and suddenly the agent finds the right functions with a plain search.
  9. Pocock opened The Pragmatic Programmer still in plastic and felt it was written for today. Agents produce software entropy faster than humans ever did. His big three now are that book, John Ousterhout on deep modules, and the first chapters of the Evans DDD book.
  10. Save planning for work that is hard to reverse. His rule is blunt. A five line fix gets aligned after the fact, a new page gets grilled first, a Stripe clone gets wayfinder. Prototypes are nearly free now, so he builds three or four and picks a favorite before writing the spec.

Related TMFNK Content

Crepi il lupo! 🐺