KN’s Reviews > Dependency Injection in .NET > Status Update
KN
is on page 79 of 584
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
— Feb 16, 2026 11:44PM
DI container (delegate) is optional
Like flag
KN’s Previous Updates
KN
is on page 79 of 584
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
— Feb 16, 2026 11:43PM
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
KN
is on page 51 of 584
Avoid loading configs within classes - this often implies a hidden dependency (from clients)
Instead, callers to load config then pass
Cohesion - Singe Responsibility Principle
— Feb 14, 2026 01:39AM
Instead, callers to load config then pass
Cohesion - Singe Responsibility Principle
