Matt Pocock debates outcome-driven vs ticket-driven workflows in agentic systems
mattpocockuk · x · 2026-11-15
Matt Pocock discusses agentic systems development methodology with @lopopolo and @nateberkopec, who argue that "successful, high ambition agentic systems only build for and evaluate for outcomes." Pocock says he finds the take hard to understand concretely and asks for elaboration. His position: tickets are just an implementation detail on the way to the destination—not worth much in themselves, but telling people not to use them at all seems odd. A substantive debate on outcome-driven development vs ticket decomposition in agent engineering workflows.
Related event: Debate: Is Breaking Specs into Tickets a Dead End for AI SDLC(5 posts)→
More from coding & agent
- 45 days talking to one personal AI agent: "minimum control, minimum friction" wins — perilli · 2026-11-15
- He built a company run by 50 AI agents — here's the Claude Code-powered architecture — Arindam_1729 · 2026-11-15
- T3 Code hype questioned: everyone is rebuilding it, few real wins yet — IndraVahan · 2026-11-15
- Free course maps the 4 ways generative media demos break in production — Al_Grigor · 2026-11-15
- Team builds custom inference engine in 4 days for $500 in tokens, beats SGLang by 15% with 6 prompts — IgorCarron · 2026-11-15
- Building a coding agent from scratch: one diagram of the agentic loop — sharpeye_wnl · 2026-11-15