What if my team isn’t using best coding practices?

I know that an engineer's job is to deliver value to the company, it's not to write the best code possible, or to be the best at following industry standards, practices, et cetera. It is to make money. You get paid, you make money for the company. It's fair. But when you have to go against this internal sensor that you have, generally, people do have a core of these values that they try to follow in order to do good work. You violate those principles enough and you get less happy, and you know your work is not the best.

And you can see the issues that will accumulate in the process, because the industry standards exist for a reason. And very often they are in conflict with a given business' objectives. There's always the slider between quality and delivery. And what I've been doing at least to mitigate that, is go in any given project, where is the slider? What are we doing right now? Are we doing delivery, or are we doing quality? And time considerations come into that. And then that's a more evolved way of handing that, I suppose, because you can then say, "Well, if we're doing delivery, now we can make provisions for quality later."