totally familiar with that - more often than not (in that it's always been the case) that is a function of how the company chose to build things, however, and not the base framework the product was built on.

in fact, the greatest source of that kind of trouble, in my experience, is constantly changing approaches and paradigms and patterns throughout the codebase to do something "more modern" without fully committing, leading to a super stratified codebase with dozens of patterns and weird hooks and bindings to make them all get along...