On the one hand I agree with the negativity somewhat. One has to get used to writing worse code than one would like.
Or be genuinely unable to distinguish good from bad code (but nobody thinks they're that guy/gal).
To help with accepting ugly code, it's good to keep in mind that no two people agree what's perfect, and in particular nobody thinks anybody else's code is perfect. Sometimes it later turns out others were right after all (usually not, but keep that option open).
On the other hand, one has to fight back a bit to make the code better than would be convenient. Take a bit more time than ugly code would take. Request budget for the most important re-factoring. Add an auto-formatter to the build chain.
In the long term it helps the company to have maintainable code. If management can't see that, then perhaps it's on us. We're the experts, after all.