Sitecore Service Locator Pattern or Anti-Pattern? For a long time now I have considered the Service Locator an Anti-Pattern, but recently I have come to question this resolve, is it black and white? Maybe not. Mark Seemann first introduced
Sitecore Two containers are better than one. Sitecore is a fantastic CMS that does many things right, and from version 8.2 the list also included Dependency Injection. It's great to see the product embrace IoC, the framework's code is
Software Craftsmanship Plugins, why should I care? In my last post, Watch your Composition Root, while exploring how I keep my bootstrapping code nice and tidy, I point out that the approach workes very well when implementing the plugin pattern.
Dependency Injection Watch your Composition Root IoC is a great pattern that can help make business logic easier to maintain and independently test, all while decreasing complexity. However, in large applications object dependency graphs can become quite complicated making
Software Craftsmanship One, One Responsibility HA HA HA HA! Over the past five weeks, I have been sharing my understanding of the SOLID principles with my team. Now being at the end of week five I wanted to share this understanding with
Design Patterns A new year and a new reason I was lying in bed this morning thinking about what I achieved in 2013. Travelled through Southeast Asia, Japan, and China. Walked the last 200km of the “Camino de Santiago”. Travelled around Ireland.
Pseudo Code Back to basics For the past two years I have been striving to become a “Software Craftsman“, this has taken re-education on how I approach programming. It has been a roller coaster ride, learning about programming
Software Craftsmanship No Test No Beer I tweeted an image a while back and thought I would share it here as well. This is classic and would make for great motivation, but there is a good point behind it.
