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

down” Client: “Get back to me, after one minute.” Chaos Engineering “If something hurts, do it more often!” Chaos under control Chaos Engineering • You learn how to fix the things that often break Inject latency Inject failure Chaos Engineering Set expected SLA Inject Failures Measure services meet SLA? E S Improve system Chaos Engineering Principles • Build a Hypothesis around Steady State Instance mic ros erv ic e s t at eles s q u i c k r e s t a r t fault tolerance c haos engineering Reserved Instance Spot Fleet Auto Scaling Fault and Recovery Oriented Architecture Spot Instance

for developer teams only starting to transition to Kotlin from Java, as many of the high level principles and policies they’re already used to will still apply. Of course, if this is the case for you encryption-related concerns that are simply fixed with a policy switch to the strict use of the protocol. The principles, standards, and practices in other programming languages where these attacks also occur are generally information’s integrity quality. • Lack of code obfuscation: This makes app code susceptible to reverse engineering. Someone with enough technical know-how can make use of non-obfuscated code to reverse engineer

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

Discussion Panel on Engineering Principles - Jakub Daliga, Lukasz Gut 4. Afterparty, slowly moving to a place close byLooking for speakers! • Golang specifics • Software engineering (implement/use/best

Discussion Panel on Engineering Principles - Jakub Daliga, Lukasz Gut 4. Afterparty, slowly moving to a place close byLooking for speakers! • Golang specifics • Software engineering (implement/use/best

Discussion Panel on Engineering Principles - Jakub Daliga, Lukasz Gut 4. Afterparty, slowly moving to a place close byLooking for speakers! • Golang specifics • Software engineering (implement/use/best

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