Prefer to do DO over DI


Today, accidentally, we invented a new term: Dependency Objection :)

We started using dependency objection in design by preventing dependencies so that we don't need to inject them anymore later. Thus prefer to do DO over DI.



Interesting... Could some people misunderstand it and while DO they re-invent the wheel? :)

Indeed, Nice thought. However the follow on thought might help ...Once there is a need, which originally you didn't foresee, one has to refactor code and then do the DI. Am I on the right track? I think this is also important, so it does not seem that the DO is irreversible.

About this Entry

This page contains a single entry by Bas Vodde published on June 21, 2012 6:23 PM.

Waterfall strikes again? -> Singaporeair site s*cks was the previous entry in this blog.

Book Review: There's always a duck is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.