Breaking Dependencies: The SOLID Principles Klaus Iglberger, CppCon 2020 klaus.iglberger@gmx.de2 Klaus Iglberger C++ Trainer since 2016 Author of the C++ math library (Co-)Organizer The SOLID Principles Single-Responsibility Principle Open-Closed Principle Liskov Substitution Principle Interface Segregation Principle Dependency Inversion Principle9 The SOLID Principles Single-Responsibility Inversion Principle Robert C. Martin Michael Feathers10 The SOLID Principles11 The SOLID Principles I will introduce the SOLID principles … … as guidelines not limited to OO programming … as general

Being Friendly to Your Hardware Performance Engineering A gentle introduction to hardware for software engineers 2Where does C++ run? 3On an abstract C++ machine 4On an abstract C++ machine?

Quantifiability Definition Vector Space System Model Entropy Measurement Correctness and Performance Engineering Case Study: k-FIFO Queue Design and Implementation of Quantifiable Stack/Queue Live Demonstration e. denotational, not small step operational) ▶ Correctness is binary, lacking any metric for engineering trade-offs ▶ Forced to make assumptions about abstract data type and object semantics (i.e. a First Principles Inspired by Descartes Applying Cartesian thought to concurrent systems, we see that first principles describe what the program does (what is programmed), while secondary principles such

Dependency Injection in C++: A Practical Guide CppCon 2024 September 18, 2024 Pete Muldoon Senior Engineering LeadBloomberg 4 Questions #include HereWho Am I? Bloomberg 5 • Started using a consultant • Bloomberg Ticker Plant Engineering Lead • Talks focus on practical Software Engineering • Based in the real world • Demonstrate applied principles • Take something away and be able to use Usage) Software Development Completeness : Knowing when you are done and why it matters Other Engineering talks by yours truly :Questions? 125 Bloomberg Contact : pmuldoon1@Bloomberg.net Bloomberg is

conditions, signed/unsigned, etc. ▪ Not always identifying the problem ▪ Not much in the way of principles to apply ▪ Formation of SG23 - Safety and Security Kona 2022 Evening Session 38DIRECTION GROUP40 fully initialized (its value can’t change until assigned) ▪ Can reject in non-conforming modes ▪ Principles on applying it to current UB ▪ P2973 Erroneous behaviour for missing return from assignment ▪ (as a whole) safety experts ▪ Many of the solutions proposed are ad hoc ▪ We (desperately) need principles we can apply ▪ SYCL ▪ Subset of customers that have specific and critical requirements ▪ Formation

15 years in Trading and Defense • Today’s talk - Engineering low-latency trading systems - Profiling techniques to find bottlenecks - Some principles along the way4 “All that we know, all that we are programming is also a losers’ game! - It’s mostly about being very disciplined… - … and not over-engineering your system • In the trading game, time to market is an important “latency” too!137 Credits

2024Hyrum's Law 36 Hiding your Implementation Details, Amir Kirsh @ CppCon, 2024 (“Software engineering at Google: lessons learned from programming over time”): - Developers come to depend on all observable Hiding your Implementation Details, Amir Kirsh @ CppCon, 2024 Less code to decommission! Software Engineering Completeness : Knowing when you are done and why it matters Peter Muldoon44 Hiding your Implementation your Implementation Details, Amir Kirsh @ CppCon, 2024 Hiding rules go well with known design principles: Encapsulation: Protecting Object Integrity. Exposing necessary interfaces only. Internal changes

last 20 years, the de-facto standard in robotics has been (informally) Component Based Software Engineering ● Multi-process and multi-nodes, distributed systems. ● Lot of inter-process communication. novel pre-post condition extension, that reduces complexity, when dealing with states.Main Design Principles 1. Productivity 2. Composability 3. ReusabilityNodes and Trees These are your reusable Tree Nodes

The Debugging Process – In Theory – And Practice 16 • There's an analogy here with software engineering processes... Simple cases - waterfall Complex cases – iterative and incrementalCppCon 2021 – Back invariants, pre-conditions, post-conditions, and self-test complex components • Consider employing the principles of test-driven design • Implement test assets in parallel with the solution • Employ good configuration

function or variable Changing system con�guration Updating build system toolchain “Software engineering is programming integrated over time.” - Titus Winters6 Aurora Innovation It takes 23 days for Good test systems report insights as output, not raw test results .25 Aurora Innovation Design Principles Developer Friendly Designed for everyday use by developers. Should enable creating tests that