4 ms·

Well stated and agreed with in the final paragraphs but why drop the half written anecdote? Also I think you may be conflating DI with testability. Items can b

Well stated and agreed with in the final paragraphs but why drop the half written anecdote? Also I think you may be conflating DI with testability. Items can be u nit testable and easy to di while not being built for it. I write code that is testable and it generally happens to be di-able as well but that's not the goal. From my own experience.

loup-vaillant 9y ago
> why drop the half written anecdote? Anecdotes are still a valuable in that they point out where you might be interested in looking further. You can't trust anecdotes, but they may indicate where to look. > I think you may be conflating DI with testability. I'm conflating DI with a stupidly narrow idea of testability. I'm fully aware that my code was easily testable (and thoroughly tested!) despite hard coded dependencies.