I couldn't say unless I looked at source code, but my thinking is that it's probably suffers from "enterprise coding". This is typical for large organizations a

I couldn't say unless I looked at source code, but my thinking is that it's probably suffers from "enterprise coding". This is typical for large organizations and it's basically over-engineering for the purposes of process and organization, instead of purely technical or product reasons. In this environment readability and unnecessary conventions take priority over reusability... this means you will recreate a button, dropdown, or API logic over and over again because it's too risky to share code across teams (because of how the org works). This is hard to really summarize but it's very clear to me when I'm working in enterprisy codebases. The development experience is painful, the processes are needless, and appearance of progress is more important than actual technical progress.