Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2FDfJC1. Nathan Äschbacher talks about how Chaos Engineering and chaos experiments on the complex data, interfaces, and algorithms used in autonomous vehicles should be a minimum requirement in validating operational safety. Äschbacher thinks we should shift towards working with chaos instead of against it, in order to build safe, reliable, and increasingly deterministic complex systems. Filmed at qconsf.com. Nathan Äschbacher is chief technology officer at PolySync. He has turned his attention---perhaps better stated as "crippling anxiety"---toward the concerns of understanding and advancing functional-safety of the software stack in autonomous vehicles and advanced driver assistance systems.

1. Chaos:
The Last Stand
Against Our Robot
Overlords
Nathan Äschbacher
@gen_nja

2. InfoQ.com: News & Community Site
• Over 1,000,000 software developers, architects and CTOs read the site world-
wide every month
• 250,000 senior developers subscribe to our weekly newsletter
• Published in 4 languages (English, Chinese, Japanese and Brazilian
Portuguese)
• Post content from our QCon conferences
• 2 dedicated podcast channels: The InfoQ Podcast, with a focus on
Architecture and The Engineering Culture Podcast, with a focus on building
• 96 deep dives on innovative topics packed as downloadable emags and
minibooks
• Over 40 new content items per week
Watch the video with slide
synchronization on InfoQ.com!
https://www.infoq.com/presentations/
chaos-engineering-reliability

3. Purpose of QCon
- to empower software development by facilitating the spread of
knowledge and innovation
Strategy
- practitioner-driven conference designed for YOU: influencers of
change and innovation in your teams
- speakers and topics driving the evolution and innovation
- connecting and catalyzing the influencers and innovators
Highlights
- attended by more than 12,000 delegates since 2007
- held in 9 cities worldwide
Presented at QCon San Francisco
www.qconsf.com

4. Freezing Robot Problem:
Once the environment surpasses a certain
level of dynamic complexity, the path planner
decides that all forward paths are unsafe.

10. 01101 26262

11. When are the models done?
01101

12. Eleventy-Bazillion
Miles

13. How do you know the software is safe?
01101

14. ¯_(ツ)_/¯

15. How do you know the software is safe?
26262

16. MISRA

17. HARDrealtime

18. 26262

20. But the AI isn’t deterministic, so…?
26262

21. ¯_(ツ)_/¯

22. ಠ_ಠ

23. 2626201101

24. Formal Methods
Model Checking
Deductive Verification
Local Testing
Property-Based
Fuzz
Unit / Acceptance
Implementation
Integration Testing
Chaos
Mutation

25. It’s not all about introducing chaos to the
system. It’s about the chaos inherent in the
system itself.
Chaos Engineering is about engineering
practices that help us surface those systemic
effects.
-- Casey Rosenthal
Traffic & Chaos Manager
Netflix
“
”

26. Control
Decision
Perception

29. ಥ_ಥ

30. +

34. ”
-- Principles of Chaos
“
”
Chaos strongly prefers to experiment directly
on production traffic.
-- Chaos Engineering
the Book
“ We don’t expect engineers to inject noise into
the sensors of self-driving cars containing
unsuspecting passengers!

35. “
”
-- Chaos Engineering
the Book
However, we suspect most users are not
working on these kinds of safety-critical
systems.

40. Over-Engineering

41. Unit
Software FEA ?Chaos
Integration
Property-Based
Form
al M
ethods
Fuzz

42. Good ol’ Engineering

46. Watch the video with slide
synchronization on InfoQ.com!
https://www.infoq.com/presentations/
chaos-engineering-reliability