Presentation: The Reinvention of the Dev Team
Engineering leaders are rethinking team structure as agentic coding forces a choice: speed or sustainability.
Why it matters
Hannah Foxwell frames the operational shift agentic dev tools demand—not just faster shipping, but rethinking on-call, skill composition, and what 'safety' means when velocity is automated. Practitioners building or leading teams adopting agentic coding will recognize the three anchors as a framework for resisting pure acceleration culture.
The key facts
8 to knowThree anchors for agentic dev teams: building software worth building, prioritizing automated safety over speed, preserving generalist 'broken comb' skillsets
Sustainable on-call practices as counterweight to agentic velocity
Presentation framed around team dynamics, not tool adoption
Published October 7, 2026 on InfoQ
Three anchors for agentic team dynamics: building software worth building, prioritizing automated safety over speed, preserving human element
Emphasis on 'broken comb' generalist skillsets over pure specialist depth
Sustainable on-call practices positioned as prerequisite for agentic velocity adoption
Source: InfoQ presentation (opinion/synthesis, not new empirical data or deployment case study)
Go to the source
InfoQ AI/MLinfoq.com
Publisher excerpt: Hannah Foxwell shares how the surge of agentic coding forces engineering leaders to rethink team dynamics. She discusses three key anchors for navigating AI-driven velocity: building software worth building, prioritizing automated safety over speed, and preserving the human element through…