If you know there are better practices you should follow, then take the few extra moments to implement them. If you don't know of good practices, start compiling a list, asking questions, even post an idea or question in the discussion for this editorial.
I think it is important to understand why something is a better practice. Can we always distinguish between something that is "best practice" and something which is merely a personal preference?
If someone asks why a particular thing is standard, then there should always be a well argued reason for it.
I've seen people impose rules forbidding views, triggers, CTEs and cascades on foreign keys among other things - I have never been given a convincing explanation of why these things shouldn't be used. If you understand how to use these things properly then they are perfectly legitimate. Views in particular are an absolutely fundamental part of an RDMBS and are the relational way of introducing reuse.
I try to avoid using temporary tables, if you ask me why, I hope I would be able to give you a convincing argument why. But notice I say "avoid" not "never".