A few days ago, while scrolling on twitter, the following tweet raised my attention. In theory, DI is a software engineering technique to build relations between objects. [...] My mission was to prevent the kind of code changes shown in my previous patch. [...] The most visible benefit of DI here is that it prevents abusive code changes and makes code extensibility easier. This is how you can achieve this: Adopting DI made the code base extensibility/maintainability so easy that the CEO of the company decided that there is no need to keep me in the team anymore…