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

Open Discussion on Project Planning Planning in an Agile Environment Key Tenets  Planning should focus strongly on the near term  Eliminate waste caused by planning for eventualities that never come at every levelSystems Engineering Role Program leaders must encourage systems engineers to engage developers, testers, users, and other stakeholders in their disciplined engineering processes. (No ivory ivory towers) While Agile systems engineering involves frequent informal technical and programmatic reviews, this less formal approach does not equate to less rigor. Instead, greater frequency allows key

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? Processor cores + Interconnect + Memory 16 Complex and scary And mostly out of scope of our discussion anywayMemory 17 • Addressable capacitor array • Short term nonvolatile • Speeds – capacitor An open question remains – what is the ratio of cores doing the former and the latter? 110Discussion 111

Prompt Engineering Author: Lee Boonstra Prompt Engineering February 2025 2 Acknowledgements Content contributors Michael Sherman Yuan Cao Erick Armbrust Anant Nawalgaria Antonio Gulli Simone Cammel Grace Mollison Technical Writer Joey Haymaker Designer Michael Lanning Introduction 6 Prompt engineering 7 LLM output configuration 8 Output length 8 Sampling controls 9 Temperature 9 Top-K and top-P 29 Self-consistency 32 Tree of Thoughts (ToT) 36 ReAct (reason & act) 37 Automatic Prompt Engineering 40 Code prompting 42 Prompts for writing code 42 Prompts for explaining code 44 Prompts for

No Silver Bullet – Essence and Accident in Software Engineering Mike Ballou“There is no single development, in either technology or management technique, which by itself promises even one order-of- published The Mythical Man-Month: Essays on Software Engineering • In 1987, authored No Silver Bullet – Essence and Accident in Software Engineering“We hear desperate cries for a silver bullet – something

coffee/beer/food; 3. 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

coffee/beer/food; 3. 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

coffee/beer/food; 3. 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

eleven charts that help illustrate observations that follow. We hope this compilation adds to the discussion of the breadth of change at play – technical / financial / social / physical / geopolitical. No are doing to illustrate trending during this uniquely dynamic time. Our goal is to add to the discussion.• Seem Like Change Happening Faster Than Ever? Yes, It Is • AI User + Usage + CapEx Growth = Unprecedented Stanford University… 1: AI ‘Winter’ was a term used by Nils J. Nilsson, the Kumagai Professor of Engineering in computer science at Stanford University, to describe the period during which AI continued to

approach, program managers need to work with stakeholders representing the requirements, systems engineering, contracting, cost estimating, and testing communities to design processes around short releases government-contractor teams. Agile cannot solve all of the DoD’s IT acquisition challenges, but offers a set of principles that can help reduce cycle times and risks to deliver IT in a complex environment. “The US joint Agile within the unique and complex DoD acquisition environment. This guide seeks to adapt proven principles of Agile development specifically to the DoD context. More and more federal acquisition programs