Status Updates From Dependency Injection in .NET

Manual DI: Constructor injection can be… verbosome but is explicit about what’s the dependencies; which is the whole point

DI container (delegate) is optional

Data (raw, dumb) object -> Domain objects: make testing easier
DI -> Composition root (DI container is optional)
Prefer interfaces over abstract classes
* make everything easily swappable
* delegate (eg to adaptees; after possibly complex conversations hidden from clients)
* avoid tendency of creating “god objects”

Minimize “volatile deps” for loose coupling, code reuse, increased testability

Avoid loading configs within classes - this often implies a hidden dependency (from clients)
Instead, callers to load config then pass

Cohesion - Singe Responsibility Principle