Fighting AI with AI — Lawrence Jones, Incident
Skills:
AI Systems Design80%
Incident's AI SRE runs hundreds of prompts per investigation across logs, metrics, traces, and code. When it produces a wrong root cause analysis, there is no tractable way for a human to read through the full trace and find where the reasoning went sideways. Lawrence Jones, founding engineer at Incident.io, describes the moment the team realized they needed AI to debug their AI.
The talk covers three patterns they built. A small CLI lets coding agents read and edit eval YAML files that had grown too large for agents to work with directly, enabling a red-green runbook where the agent writes a failing eval, fixes the prompt, and checks nothing else broke. Their bigger unlock was serializing every UI debugging view as a downloadable file system: drop it into a Claude Code session, describe the bad behavior, and the agent traces through the prompt hierarchy to tell you exactly which prompt to change. For fleet-scale analysis, 25 agents run in parallel each analyzing one investigation, then a second stage clusters the results to surface systemic failure patterns across customer accounts.
Speaker info:
- https://x.com/lawrjones
- https://www.linkedin.com/in/lawrence2jones/
Watch on YouTube ↗
(saves to browser)
Sign in to unlock AI tutor explanation · ⚡30
More on: AI Systems Design
View skill →Related AI Lessons
⚡
⚡
⚡
⚡
How I Built a YouTube Shorts Brief Generator with PHP and the OpenAI API (in a Few Hours)
Dev.to · James Dudley (James)
Best AI Writing Tools 2026 — Tested & Compared
Dev.to AI
How AI is Redefining Creativity and Productivity in 2026 (Top Tools Ranked)
Medium · AI
AI as Your Quality Control Partner for Grant Proposals
Dev.to AI
🎓
Tutor Explanation
DeepCamp AI