A Developer's Guide to Not Getting Replaced by Agents

Описание: The best agentic developers throw away their agent's work without guilt, run three agents at once and only use one, and treat their AI like a junior developer they genuinely dislike. It sounds wrong. It works.

Daniel Jones, head of product at re:cinq, has upskilled hundreds of developers across Northern Europe's largest enterprises. In this episode he joins Simon Maple to share the counterintuitive habits, hard data, and practical frameworks behind high-performing agentic development teams.

On the docket:
• Why bad engineering practices get worse, not better, with AI agents
• The exact conditions that make your agent hallucinate every time
• Why your AGENTS.md is quietly working against you
• How to manage context before it kills your productivity
• What enterprise AI rollout actually looks like at scale
• Why the worst managers get the most out of agentic coding

If your team is adding AI and wondering why things aren't getting faster, this episode is for you.

Connect with us here:
Daniel Jones:   / danieljoneseb  
Simon Maple:   / simonmaple  
Tessl:   / tesslio  

(00:00) Trailer
(01:10) AI DevCon
(02:03) Introduction
(03:42) Good engineering practices for agentic development
(06:02) Why tests matter for agents
(09:36) Version control and commit hygiene
(13:56) Safety and containerisation
(18:53) Spec-driven development and user stories
(21:48) Tool selection across organisations
(26:33) Context management fundamentals
(30:38) Managing skills and MCP servers
(34:43) Sharing context across teams
(38:25) Understanding hallucinations
(41:43) Agents vs LLMs explained
(46:10) Non-determinism and superstition
(49:52) Measuring skill effectiveness
(53:01) Platform teams and rollout
(56:42) Tips for developers
(57:42) Tips for organisations
(59:01) The future of agentic development