I will explain what troubles a badly written class could bring and present a way to replace it with a better solution -- using good practices and design patterns. The first part is for every developer who knows C# language basics - it will show some basic mistakes and techniques to make code readable like a book. The advanced part is for developers who have at least a basic understanding of design patterns -- it will show completely clean, unit testable code.
Alternatives
Members may post updates or alternatives to this current article in order to show different
approaches or add new features.
No alternatives have been posted.