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...
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...
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.