Jacob Miller and Jeremy Mumford, authors of 'Architected Intelligence', discuss the enduring principles for building successful AI products and organizations. They cover why velocity is the only durable moat, why hallucinations are a data curation issue, and the proper progression from skills to workflows to agents, emphasizing a shift from focusing on models to focusing on process and speed.
Explore advanced techniques for building long-running AI agents, moving beyond simple loops. Learn why self-evaluation fails and adversarial evaluators succeed, how to manage context with structured handoffs instead of just compaction, and how to use negotiated 'sprint contracts' and detailed rubrics to build and test complex, full-stack applications autonomously.
AI agents are having a moment, and understanding MCP and ADK is key to building them well. Cedric Clyburn and Anna Gutowska explain how MCP powers tool integration while ADK structures reliable multi‑agent systems 🤖. Learn when to use each to build more capable and predictable AI agents.
AI agents introduce a critical security gap when connecting to legacy enterprise systems, known as the 'agentic last mile identity problem'. This summary explains how losing user identity, context, and delegation breaks zero-trust principles and outlines a solution using a policy-driven vault to manage access and issue short-term credentials.
A case study from PFF reveals how a two-engineer team, by leveraging AI agents, achieved a 25x increase in deployment frequency and 10x the output of a ten-engineer team. CTO Mike Spitz explains their core principle: shifting focus from making engineers faster to making AI agents faster. This talk deconstructs the resulting transformation, which eliminated traditional agile ceremonies like stand-ups and sprint planning in favor of an automated, spec-to-PR workflow, redefining the roles of engineers and processes in a modern software organization.
Intercom doubled its engineering throughput in under a year by treating its AI coding agent not as a simple tool, but as a new senior engineer. This involved a full onboarding process onto their 15-year-old Rails monolith, creating a library of durable skills for recurring tasks, and providing audited access to all internal systems.