Writing sustainable software. The how and the what!
summary
Shows concrete C++ patterns and working code from the iceoryx middleware: a type-state pattern that moves ownership through distinct types so invalid call orders fail at compile time, bespoke STL-like types and a bucket allocator because production runs with no heap no exceptions on autonomous vehicles, and functional APIs (callbacks wrapped in optional/monadic styles) that cut error-handling and concurrency hazards. Demonstrates these designs compiled under C++14 and used in production.
AI-written summary · about
chapters (15)
- 0:00Start
- 6:21Is the Design over Abstracted
- 9:59Is this Api Easy To Use and Hard To Misuse
- 11:44What Is the Type State Pattern
- 13:40Design by Contract
- 14:56Hidden Transition of Ownership
- 17:12Can We Reduce the Error Handling
- 26:21How Could I Name Functions and Methods
- 30:46Enums Are Extendable
- 31:10Can the Api Be Used without Documentation
- 36:28Functional Approach
- 42:27Factory Methods
- 47:56Is the Code Expandable
- 57:32Recursive Mutex
- 59:36Bucket Allocator
