One thing that I've noticed in my time working in large Java server codebases is that there seem to be a number of broad categories of code (not mutually exclus

One thing that I've noticed in my time working in large Java server codebases is that there seem to be a number of broad categories of code (not mutually exclusive, just one breakdown, and not exhaustive): * framework - dictating how people should do things like request handlers, how work is scheduled * feature - making something new work * wiring - the binary had this information in it in this codepath, but we also need it in this other place... And I have found that DI tends to be the magical "will write code for you" thing that mostly replaces the third one.