## Breaking Dependencies: The SOLID Principles Klaus Iglberger, CppCon 2020 klaus.iglberger@gmx.de ## C++ Trainer since 2016 Author of the bl $ \text{ze} $ C++ math library (Co-)Organizer of the Munich The SOLID Principles Single-Responsibility Principle Open-Closed Principle Liskov Substitution Principle Interface Segregation Principle Dependency Inversion Principle ## The SOLID Principles Single-Responsibility (Redirected from SOLID (object-oriented design)) ## Concepts [edit] This article is about the SOLID principles of object-oriented programming. For the fundamental state of matter, see Solid. For other uses

# 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 every level ## Systems 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

coffee/beer/food; 3. Discussion Panel on Engineering Principles - Jakub Daliga, Lukasz Gut 4. Afterparty, slowly moving to a place close by ## Looking for speakers! • Golang specifics • Software engineering (implement/use/best

# Prompt Engineering Author: Lee Boonstra Google  ## Acknowledgements Content contributors Michael Sherman Yuan Cao 36a0d02d290d979fb4e8519f2fef1/p2_1.jpg) ## Table of contents Introduction.....6 Prompt engineering.....7 LLM output configuration.....8 Output length.....8 Sampling controls.....9 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

September 15 - 20 ## +24 ## Performance Engineering Being Friendly to Your Hardware ## I GNAS BAGDONAS ## Being Friendly to Your Hardware Performance Engineering A gentle introduction to hardware for f0b3b420b58b2e5986f32263a8e4e3f/p16_1.jpg) Complex and scary And mostly out of scope of our discussion anyway  ## Memory too • An open question remains – what is the ratio of cores doing the former and the latter? ## Discussion

## 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-magnitude published The Mythical Man-Month: Essays on Software Engineering • In 1987, authored No Silver Bullet – Essence and Accident in Software Engineering  # No Silver Bullet —Essence and Accident in Software Engineering Frederick P. Brooks, Jr. University of North Carolina at Chapel Hill There is no single development

coffee/beer/food; 3. Discussion Panel on Engineering Principles - Jakub Daliga, Lukasz Gut 4. Afterparty, slowly moving to a place close by ## Looking 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 by ## Looking for speakers! • Golang specifics • Software engineering (implement/use/best

Kubernetes and containers Cloud-Native DevOps A DevOps Operating Model GitOps Principles Declarative Versioned and Immutable Pulled Automatically Continuously Reconciled and to brain-dump the details into meetings, documents, glossaries, and more. We built the GitOps Principles $ [3] $ based on knowledge and feedback from a wide swath of industry experts. We organized multiple ol-for-kubernetes-doesnt-exist/ [2] https://youtu.be/UvwcVNv61Mo [3] https://opengitops.dev/#principles ## I ntroduction As Christian was writing this book, I had the pleasure of learning alongside

## Over engineering the core of Kubernetes kops Kris Nova ## Kris Nova ## About Me   ##### “I speak for the software...” ## Over Engineering Go in Kubernetes ## So what did we over engineer? ## Kubernetes Kops Kubernetes Operations A ##