In 2007 there was a movement in the .NET community dubbed “ALT.NET”. A community was formed by individuals who believed there to be a “better” way from the tooling, frameworks, practices and principles provided by Microsoft. The initial release of Linq to Entities (Entity Framework) was really a starting point for discussion since it did not support POCO’s and was not persistence ignorant. ALT.NET was about challenging the status quo. Although some might not be familiar with with the ALT.NET movement, you can thank it for helping the common practice of: Inversion of Control (Dependency Injection), Persistence Ignorant ORM’s, and… Read More »Status Quo
Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.
Before I post too many SOLID principle posts, let me prefix by saying that I strongly believing that following SOLID principles as guidelines will lead to writing better Object Oriented code. Back to Open/Close Principle… Software entities like classes, modules and functions should be open for extension but closed for modifications. Out of all the SOLID principles, I’ve found this one to causes the most confusion and is the hardest to identify for developers. When following any of the SOLID principles, they all have a bit of cross over that help you identify when violating one of them. Violating Open/Close… Read More »Open/Closed Principle Violation