Comments on: Dependency Injection and Inversion of Control are not rocket surgery

By: Garry Pilkington

Garry Pilkington — Thu, 05 Nov 2009 09:54:32 +0000

Great example. I have bookmarked this and will use it to show my colleagues just how simple DI and IOC are.

By: Tweets that mention Dependency Injection and Inversion of Control are not rocket surgery | Lazycoder -- Topsy.com

Wed, 04 Nov 2009 17:57:58 +0000

[...] This post was mentioned on Twitter by Scott Koon, Ryan Farley, Jungchan Hsieh, Patrick Veverka, Doug Philips and others. Doug Philips said: RT @lazycoder: [posted]Dependency Injection and Inversion of Control are not rocket surgery http://bit.ly/1AjGZN [...]

By: Dew Drop – November 4, 2009 | Alvin Ashcraft's Morning Dew

Dew Drop – November 4, 2009 | Alvin Ashcraft's Morning Dew — Wed, 04 Nov 2009 13:24:01 +0000

[...] Dependency Injection and Inversion of Control are not rocket surgery (Scott Koon) [...]

By: Reflective Perspective - Chris Alcock » The Morning Brew #469

Reflective Perspective - Chris Alcock » The Morning Brew #469 — Wed, 04 Nov 2009 08:28:08 +0000

[...] Dependency Injection and Inversion of Control are not rocket surgery – Scott Koon shows how the techniques of Dependency Injection and Inversion of control are not as complicated as may developers believe, looking at definitions of the techniques and showing simple examples of both. [...]

By: Damian Brady

Damian Brady — Tue, 03 Nov 2009 23:51:38 +0000

That’s probably the best description of these concepts I’ve seen.

I have to be honest, I was fairly confused by DI and IoC the first time I saw them. I wish I’d seen an article like this right at the start – it would have made things a lot easier.

Thanks, I’ll be passing this link on.

By: Rob G

Rob G — Tue, 03 Nov 2009 21:38:07 +0000

In a word – “Quality!”

It’s posts like these that are driving home everyday something that we already know: these concepts are not tough to understand and use, it is the incessant resistance to change causing problems.

The more of these great 1-pagers we have in evidence, the more I get to point out to those whining about “if it ain’t broke…blah” – that simple changes like this to future code at the very least will pay back dividends that they cannot yet fathom.

That’s the real problem – the not being able to “fathom the benefits” part.

Great post, keep ‘em coming
Rob G

By: Scott

Scott — Tue, 03 Nov 2009 21:28:55 +0000

Wim: Yeah, I struggled a bit to come up with a good example of IoC. I finally just went with the interface injection. I supposed that delegate event handlers would have been another good example, one that might have turned on the light bulb for a lot of people. “Oh, I’m already using IoC and I didn’t even know it”.

By: uberVU - social comments

uberVU - social comments — Tue, 03 Nov 2009 21:26:28 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by lazycoder: [posted]Dependency Injection and Inversion of Control are not rocket surgery http://bit.ly/1AjGZN...

By: Wim Hollebrandse

Wim Hollebrandse — Tue, 03 Nov 2009 21:15:55 +0000

Dependency injection really is something that enables inversion of control. It doesn’t have to be the case. In your reader example IoC isn’t very clear at all.
In my opinion IoC is more about having a container that really controls a fairly granular set of methods defined on the dependency interface definition but the container wraps its own logic, logging, and process of executing the interface methods.

Good and sensible post though – you can easily roll your own specific IoC container, it’s just that some of the abstract factory and configuration aspects are mostly taken care of when using an existing IoC framework.

By: Ryan Farley

Ryan Farley — Tue, 03 Nov 2009 21:02:40 +0000

“Rocket surgery” LOL