Why your agents need decision traces, not just documents — Zach Blumenfeld, Neo4j

This talk addresses the challenge of maintaining consistency and understanding in software development, particularly with the advent of AI agents. It proposes a system for capturing and enforcing decisions using established documentation practices like Architecture Decision Records (ADRs), Product Requirements Documents (PRDs), and Behavior-Driven Development (BDD). The core thesis is that by formalizing why and how decisions are made, developers and AI agents can operate more effectively and consistently.

This talk introduces context graphs as a method to enhance AI agents' decision-making capabilities. By integrating knowledge graphs with AI agents, the goal is to move beyond simple knowledge provision to enabling agents to understand and act upon rules and policies, thereby making more informed decisions. This approach aims to fill the gap in AI agents' reasoning by providing them with the necessary context and decision-making frameworks.

This talk explores the potential pitfalls of rapid software development fueled by AI, emphasizing the importance of deliberate decision-making and high-quality craft over sheer speed. It argues that while AI tools can accelerate development, they may lead to a proliferation of mediocre or confusing products if not guided by a strong sense of taste and user focus. The conversation highlights the need for engineers to maintain a critical perspective, prioritizing user needs and product quality even as development cycles shorten.

This talk explores the challenges and potential pitfalls of using AI agents in software development, arguing that while these tools offer significant productivity gains, they can also introduce subtle forms of friction that undermine code quality and engineering judgment. The core thesis is that intentionally reintroducing certain types of friction is crucial for maintaining control, ensuring quality, and leveraging human experience in an agent-assisted development workflow.

This talk argues that fundamental software engineering principles are more critical than ever in the age of AI. The speaker critiques the "specs-to-code" movement, which suggests generating code from specifications using AI, asserting that this approach often leads to deteriorating code quality. Instead, the talk emphasizes that well-structured, understandable, and maintainable codebases are essential for effectively leveraging AI's capabilities and that AI should be viewed as a tactical tool requiring strategic human oversight.