Showing posts with label design patterns. Show all posts
Showing posts with label design patterns. Show all posts

Monday, 21 September 2015

The Dependency Inversion Principle And The Dependency Injection Pattern

Following on from a previous blog about Inversion of Control, I intend to continue by discussing the patterns identified in that article as being IoC patterns, or rather implementation patterns which enable the application of the IoC concept. Specifically in this post we will be looking at the Dependency Injection pattern, which will be followed up by a post on the Service Locator anti-pattern.

What is the Dependency Inversion Principle?

The dependency inversion principle refers to a specific form of decoupling software modules. When following this principle, the conventional dependency relationships established from high-level, policy-setting modules to low-level, dependency modules are inverted (i.e. reversed), thus rendering high-level modules independent of the low-level module implementation details.

Monday, 14 September 2015

Did Uncle Bob get it wrong? ... a question not posed lightly

I don't mind admitting that I am a huge fan of Robert (Uncle Bob) C. Martin. I've read so much of his published material and I think he has a great deal of important stuff to say. His videos are fantastic too, you must have seen them? Well if not then I strongly suggest you search for him on youtube; there's oodles of great stuff on there all ready for your viewing pleasure.

I have always taken everything I've read or heard from Uncle Bob very seriously. I've been reading a lot of stuff on his blog (I hope he doesn't mind the link, but I'm sure it will be fine)

Anyway it is with great reluctance that I posit the notion with this question ...

Did Uncle Bob get it wrong?

One blog in particular from Uncle Bob caught my eye recently, it is entitled 'Interface' Considered Harmful and can be found here

I lapped it up, every word that had been carefully selected so as not to leave room for ambiguity. I thought it was a great post and that it helped me to realize just what it was that was bugging me about .Net. There was this little itch when I consider C#. Don't misunderstand me at all, C# is my language of choice these days, but there was something niggling away at the back of my mind and reading that blog entry brought it right to the fore.

Thursday, 27 August 2009

Inversion of Control (IoC)


What exactly does that mean?

At the heart of the matter IoC is all about loosely coupled software components.

Class1 has a member of type Class2 which is specified at design time.


Class1 has a member of type Interface1, and Class2 is an implementation of Interface1.


What is the difference between these two approaches as presented above?

The second example clearly involves more code? One might think then that in fact the first approach is better, or even that it is "cleaner"; it is quicker to write, it is simple to understand, and it results in fewer source files.

Wednesday, 26 August 2009


This blog entry is a response to an onerous blog entry which can be found here : andrewtroelsen.blogspot.com/decorator-pattern-extension-methods.html

The upshot is that the above blog entry wrongly states that you can implement the decorator pattern via .net extension methods, and further goes on to define an implementation which itself is not the decorator pattern.

Many people have commented on the original blog entry, however I don't think any of those comments goes far enough to properly explain why the original posting is wrong, or how it should actually be achieved.