Thanks a lot for reading and sharing your thoughts, Ola.

It took a while to accept that Dependency Inversion could be better named, and that explanation just helped make it make sense.

The number of files that need to change for a given change is a good indicator of how tightly-coupled a given codebase is.

Another indicator I've found could be how often a mocking framework like `jest.mock(...)` is used in tests. It sounds counter-intuitive cos mocking tools are so popular, but that's an article for another day.