How do you understand heavily decoupled code wired through dependency injection?
I'm trying to understand a C# system built around roughly 50 generic pipelines implementing Pipeline. Events are handled by many generic publishers and subscribers that implement interfaces such…