In Building Microservices: Designing Fine-Grained Systems, Sam Newman writes: The architecture of a real-world running system is never clean or pristine. If you want a “clean” architecture, by all means laminate a printout of an idealized version of the system architecture you might have had, if only you had perfect foresight and limitless funds. Real […]
We, as software engineers, know full well that requirements change. Indeed, most of us realize that the requirements document is the most volatile document in the project. If our designs are failing due to the constant rain of changing requirements, it is our designs that are at fault. We must somehow find a way to […]
I recently came across the suggestion of implementing a ColorValue type that uses an enum field to differentiate different color spaces that can be represented in C# as the following: enum ColorSpace { Cmyk, Rgb, CieLab } class ColorValue { public ColorSpace ColorSpace { get; init; } public double[]? Component { get; init; } } […]
In Design Principles and Design Patterns, Robert C. Martin presented the SOLID principles of object-oriented software design over twenty years ago. “SOLID” continues to be a buzzword included in many resumes today. The principles are reproduced here: A class should have only one reason to change. A module should be open for extension but closed […]