> it has better extendability and is more generic Those are noble goals; I think the problem arises when devs forget that "change the code" and "replace with s

> it has better extendability and is more generic Those are noble goals; I think the problem arises when devs forget that "change the code" and "replace with something else" are perfectly valid options. Adding a plugin interface and override hooks, just in case they might be needed, for an internal library, then it's a classic case of YAGNI. When an implementation is so configurable that passing it a config is more effort than writing a bespoke implementation, then it may be an example of the "inner platform effect". I wrote about this sort of thing on StackExchange a few years ago https://softwareengineering.stackexchange.com/a/382229/112115 https://softwareengineering.stackexchange.com/a/382229/11211...