I've seen this happen where there is something like an "architect / senior" vs "normal programmer" role split, where the architect can sell some stupid idea that sounds good, or make a proof of concept implementation, then throw it over the wall to someone else who needs to maintain and fix the mess.
Or if practices like code review or testing aren't done or aren't done properly, which is a way to veto or slow down bad ideas.
If the problem "trickles down" from the top of the company and you have no leverage there, I don't think there's any easy way to fix it, if any.