[newtype]

"Poorly engineered" and "over engineered" are different.

If the solution is running slow for no good reason it's poorly engineered. If it's unnecessarily difficult to implement it's poorly engineered. If it eats up too much memory because it does more than you need it for it's poorly engineered. If it's taking too long to create, it's poorly engineered.

In my experience I hear the term "over engineered" used by bitchy architects to describe components that have none of these problems, but are built, under the covers, using features of the underlying system or techniques that are unfamiliar to that architect. I hear it used to cover insecurity on teams containing members of very different skill levels.

If it's a problem, call it poorly engineered and get it fixed; if it's not a problem and you just can't read it, hit the books or get out of the way. The term "over engineered" just worries the suits, and does no good.