Welcome to the Lounge

Quote from the book:

Putting Patterns in Their Place
Design patterns provoke strong reactions, as the emails I receive from readers will testify. A substantial proportion of the messages I receive are complaints that I have not applied a pattern correctly.

Patterns are just other people’s solutions to the problems they encountered in other projects. If you find yourself facing the same problem, understanding how it has been
solved before can be helpful. But that doesn’t mean you have to follow the pattern exactly, or at all, as long as you understand the consequences. If a pattern is intended to make projects manageable, for example, and you choose to deviate from that pattern, then you must accept that your project may be more difficult to manage. But a pattern followed slavishly can be worse than no pattern at all, and no pattern is suited to every project.

My advice is to use patterns freely, adapt them as necessary, and ignore zealots who confuse patterns with commandments.

Quote:

** Managing null values - Use the null conditional and null coalescing operators
** Extending the functionality of a class without modifying it --> Define an extension method
** Expressing functions and methods concisely / Use lambda expressions
** Modifying an interface without requiring changes in its implementation classes --> Define a default implementation
** Performing work asynchronously --> Use tasks or the async/await keywords
** Producing a sequence of values over time --> Use an asynchronous enumerable