Comment by Filip Milovanović on What are the main advantages of the Dependency Inversion Principle?

Just to clarify, are you saying that people in your team are currently using dependency injection, but do it because it's a "best practice", without really understanding why - in particular, without an understanding the dependency inversion aspect of it - so they just define these interfaces based on the immediate needs of the lower-level code, and kind of haphazardly add methods in as the need arises without giving it much thought? And then this seems fine at first, but after a while there's a lot of busywork just to make a simple change?