“The design plays a much more central role in the success of a project than any feature could ever do. Good software is not primarily about the proper use of any feature; rather, it is about solid architecture and design.
Good software design can tolerate some bad implementation decisions, but bad software design cannot be saved by the heroic use of features (old or new) alone.”
(Klaus Iglberger, C++ Software Design)

Good Software Design — the proper management of dependencies — is the foundation for the success of a project. The basic building blocks for software design are design patterns. Design patterns have proven themselves invaluable over several decades and thus knowledge about them is essential to design robust, decoupled systems. Modern C++, however, has profoundly changed the way we use C++, how we think about design and implement solutions. This also affects how we implement design patterns.

This training class explores modern C++ software design and the modern forms of classic design patterns. It provides guidelines, idioms and best practices for sustainable and maintainable design, which enables programmers to create professional, high-quality code. Amongst others it will answer the following questions:

• How does good C++ design with a minimum of dependencies look like?
• What are the most important rules for robust, maintainable, and sustainable design?
• What are the most common pitfalls in C++ software design?
• Why does classical C++ design based on inheritance hierarchies fail so often?
• How are the classic design patterns implemented in modern C++?
• What are alternatives to the classic design patterns?

After this course, participants will …

• … have a detailed understanding of the essential design principles;
• … understand the benefits of separation of concerns;
• … be able to design code with minimum dependencies;
• … have an impression of the modern alternatives of classic design patterns;
• … have gained knowledge about modern design techniques;
• … understand how std::function, std::any, and ranges work;
• … favor composition over inheritance;
• … know about the importance of value semantics;
• … comprehend the advantages of non-intrusive design.

• You are not aware of the impact of dependencies on code quality
• You don’t know the SOLID principles or don’t consider them for your work
• You believe object-oriented programming is about inheritance relationships
• You consider moving functionality into classes the preferred design choice
• You want to reevaluate classic design patterns
• You want to get an impression of modern C++ design patterns
• You wonder about type erasure and expression templates or their value