In the last 15 years, I have worked for a government agency, a commercial publisher, two consultancies, and a corporate software center (current).

The consultancies often wanted the last two, even when it risked the integrity of the project, e.g. the safety and completeness of the custom application.

Often, fast meant reuse poorly conceived, designed, documented, and/or executed code written for a completely different client and/or business need.

If this is what you're facing, then jet. It's not worth the aggravation.

OTOH, if you're worried about the differences between servicable (80-95% perfect and the user knows it) versus elegant (100% perfect but nobody cares), then concentrate on the former. You'll be happier in the long run.

When writing code for hire, there's really only one benchmark: is the client happy? If so, then anything more is sugar-coating that should be avoided.