Sub parts of the Thing are described as “shared” or “reusable”… but no-one else is using them.
The Thing has lots of unit tests, but few (or no) integration tests because they are so much harder to write.
No one can explain clearly what the Thing does, because the generalised use case has obfuscated the actual problem it was originally supposed to solve.
It would be helpful to see a UML diagram of the Thing, because no one can even begin to map the dependencies in their head. Or on paper.
More time is spent worrying about elaborate corner cases than use cases.
The word “framework”.