BugBash'26: Day 2
Summary
BugBash'26 Day 2 featured diverse talks, starting with Brian Potter explaining why buildings rarely collapse, citing technical factors like 2X-3X load design and cultural elements like building codes and conservative civil engineering practices, leading to failure rates between 1/100K and 1/1M. Gary Marcus then critically assessed current AI, arguing that pure LLMs cannot achieve AGI and advocating for neurosymbolic AI, predicting AGI won't arrive until 2027 or 2028 due to a lack of "world building" and reasoning capabilities. Frank McSherry discussed building confidence in distributed streaming systems, highlighting virtual time as a powerful abstraction and emphasizing dogfooding. Finally, Gabriela Moreira introduced Quint as a TLA+ alternative for formal verification, focusing on "behaviors" for software correctness, while Steve Klabnik explored the existential impact of AI on software engineering, stressing the renewed importance of formal methods and a deeper grasp of reality in code.
Key takeaway
For AI Engineers developing complex systems, you should prioritize robust design principles and formal verification techniques. Just as civil engineers build in 2X-3X safety margins and rely on codes, your AI-driven software needs strong abstractions and spec-driven development. Embrace tools like Quint for model-based testing and simulation-first approaches to build confidence, especially as AI introduces new complexities and potential for "jailbreaking." This proactive stance mitigates risks and ensures system reliability.
Key insights
Robust systems, whether physical or digital, rely on conservative design, strong abstractions, and rigorous verification, with AI's rise amplifying the need for formal correctness.
Principles
- Conservative design and redundancy prevent catastrophic failures.
- Effective abstractions simplify complexity and prevent misuse.
- Formal methods are crucial for verifying complex system behaviors.
Method
Develop software using a simulation-first approach with deterministic simulators, and model systems as states and transitions, employing random simulation and reproducible examples for verification.
In practice
- Design systems with 2X-3X expected load and alternate load paths.
- Implement virtual time abstractions to manage nondeterminism in distributed systems.
- Utilize formal verification tools like Quint for spec-driven development.
Topics
- Structural Engineering
- AI Safety
- Neurosymbolic AI
- Formal Methods
- Distributed Systems
- Software Correctness
- Simulation-First Development
Best for: Software Engineer, AI Scientist, AI Engineer
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by Metadata.