Sure, that makes a lot of sense, and it's a sensible demand when there are a million people, each putting up one fence. However, when you write the same archit

Sure, that makes a lot of sense, and it's a sensible demand when there are a million people, each putting up one fence. However, when you write the same architecture over and over, you don't write an explanation each time - for various reasons, a not insignificant one being that there's no obvious place to put it. (I use dependency injection in my code. Where should I explain why - on each class? In a separate file in the project? In the documentation? Should I write documentation, then? What if I write it and others continue to "new" services inside their code?)