Engineering brief
Coding agents need paved roads, not solo cowboys.
At a glance
- Relevance
- Practical value
- Warnings
- None
Stop fixing agent output. Improve the system.
Agent adoption fails without organizational redesign, not better models.
Summary
Patrick Debois argues the key bottleneck in coding agent adoption is organizational, not technical. Developers
initially resist becoming 'prompt engineers,' but a new technical path opens when they build tooling
and harnesses for agents. This shifts their identity from code writers to system builders.
Watch the video
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
Why a Positive A/B Test Is Not Enough for AI Features
Bumble's PM reveals why a positive A/B test for an AI feature is only the start: low adoption, bad long-tail outputs, hidden costs, and regulatory walls.
Why Your AI Agents Need a Manager, Not Just Permissions
AI agents need HR-style governance: identity, sponsor, and machine-speed oversight. The talk from Gravitee offers a framework but no proof.
Model Choice Barely Matters: Fix Engineering Culture, Not AI Tools
AI model choice explains under 1% of developer output variance, per Jellyfish's 50,000-engineer dataset. The levers leaders control matter more.
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.