AI Dev 26 x SF | Marc Brooker: It's Time to Be Right

DeepLearningAI · Intermediate ·🤖 AI Agents & Automation ·2h ago
At AI Dev 26 x San Francisco, Marc Brooker from AWS argued that the future growth of Agentic AI depends more on reducing defect rates than on advancing model capabilities. He outlined a vision for the industry: Reliability Over Hype: He proposed moving from high-consequence errors toward a "low rate of low consequence defects" to make AI dependable for everyone. Correctness Tools: He highlighted AWS investments in "correct by construction" frameworks like Hydro and Cedar, alongside automated reasoning tools like Lean and Strata, to ensure code and policy accuracy. Auto-Formalization: He described using AI to turn natural language into mathematically precise specifications to prevent internal inconsistencies. Higher Standards: He called for a shift in industry culture to prioritize reliability, suggesting new benchmarks that measure the severity of failures rather than just their density.
Watch on YouTube ↗ (saves to browser)
Sign in to unlock AI tutor explanation · ⚡30

Related AI Lessons

Tutorial: Build a Cost-Aware AI Support Triage API
Learn to build a cost-aware AI support triage API to efficiently handle multiple complex tasks with a single endpoint
Dev.to · DigitalOcean
Don't build an AI that replays yesterday's spec — the gap between spec and source of truth is the real context
Learn to identify the gap between spec and source of truth in AI development to create more effective and context-aware AI systems
Dev.to AI
I Built an AI App That Keeps You Consistent (Not Just Motivated) 🚀
Learn how to build an AI app that fosters consistency, not just motivation, and why it matters for personal growth
Dev.to · Parth Bisht
GitLab cuts 7% of workforce and flattens management in sweeping ‘agentic era’ restructuring
GitLab cuts 7% of workforce and restructures for an 'agentic era' where AI agents write most of the code, learn how this impacts DevOps and AI development
The Next Web AI
Up next
The Agent Development Lifecycle: Build, Test, Deploy, Monitor | Interrupt 26
LangChain
Watch →