Overview

Even though many developers are familiar with the SOLID Principles, this course delves into the subtle nuances of each principle, providing examples that often lead to 'Aha!' moments. Mastering these principles will give you insights that mature your approach to software design.

The course begins by examining the symptoms of poorly designed code and demonstrates how applying certain programming principles can alleviate these issues. However, it also cautions against over-conformance: applying a principle simply because it exists can lead to new problems. Understanding when a principle is helpful, when it is harmful, and the trade-offs involved in choosing one principle over another is crucial.

The course also emphasizes the importance of designing code that is inexpensive to change. Principles and trade-offs are presented in the context of making changes easier and more cost-effective. Anticipating change and understanding the factors that drive it are central themes, serving as key discussion points and guiding design choices throughout the course.

Motivation

Many developers are aware of the SOLID Principles, but transforming this awareness into practical, effective design tools requires a deeper understanding.

Often, we recognize messy code but struggle to pinpoint the specific issues or know which principle could help. This course bridges that gap, equipping developers to identify the symptoms of poor design and apply the right SOLID principle to make meaningful improvements.

Learning Objectives

• Understand the SOLID Principles and when to apply each
• Identify symptoms of poor design and apply the right SOLID principles
• Balance trade-offs to avoid over-conformance or misuse
• Design flexible, change-friendly code for evolving needs

Target Audience

• Any software developer would benefit greatly from this training
• Suitable for integration into Internship Programs

Outline

➟ onsite: one day
➟ online: one day with 4-hour session

Commonly this course is integrated in training programs along the 'Application Infrastructure for Clean Architecture' or 'Code Desing Practices'.

• Rotting Software Smells
• Single Responsibility Principle
• Open Closed Principle
• Liskov Substitution Principle
• Interface Segregation Principle
• Dependency Injection Principle
• Lab: Code Design Example
• Don’t Repeat Yourself