A talk on designing a dependable AI execution layer that handles thousands of operations without constant supervision. The system is built to be precise, responsible, and action-oriented, avoiding common LLM pitfalls like burnout, memory bloat, and overthinking.
Three experienced software engineers—Ian Cooper, David Whitney, and Hannes Lowette—deconstruct the evolution of software architecture from a top-down, "ivory tower" practice to a modern, collaborative discipline. They explore the dynamics between emergent and intentional design, the importance of sustainable development over "slash-and-burn" cycles, and how architectural strategies must adapt to organizational scale. The conversation emphasizes that the architect's primary role has shifted to coaching, fostering a shared language, and managing trade-offs, concluding that all significant architectural challenges are ultimately people problems rooted in communication, empathy, and culture.
Anant Bhardwaj, CEO of Instabase, presents a pragmatic guide for building enterprise AI. He argues that AI agents are best used during the 'design-time' to create predictable workflows, rather than for autonomous 'runtime' operations. Bhardwaj also debunks the hype around RAG, highlighting its dependency on data quality, and explains why trust in AI systems stems from predictability, not just accuracy.
Lak Lakshmanan presents a robust architecture for building production-quality, framework-agnostic agentic systems. He advocates for using simple, composable GenAI patterns, off-the-shelf tools for governance, and a strong emphasis on a human-in-the-loop design to create continuously learning systems that avoid vendor lock-in.
Ben Kus, CTO of Box, outlines the technical evolution of their AI platform, detailing the transition from a promising but fragile LLM-based metadata extraction system to a robust, scalable agentic architecture. He explains why this shift was necessary to handle enterprise-level complexity and the key lessons learned.
Author Vlad Khononov discusses his book "Balancing Coupling in Software Design," explaining how a failed microservices project led him to rediscover timeless design principles from the 1970s. He explores the concepts of local vs. global complexity, the role of modularity as an antidote to complexity, and how managing coupling is crucial for building maintainable systems in any architectural style, from monoliths to cloud-native applications.