Best Practices is somewhat like common sense, everyone agrees that everyone should know it until any two people start discussing it in detail. No two people completely agree on the definition and there is no logical source of truth that applies to all situations.
Are you writing the guidance system for a space satellite (you probably aren't)? Then Hell No poor quality / performing code is never acceptable in this sort of work.
Are you writing a throwaway website for a one time marketing push (you probably aren't doing this either or you wouldn't have asked the question, but it is more likely than the satellite)? Then Hell Yes, get that piece of fluff out the door through any means necessary to meet deadline, the next marketing director is probably going to do something else with a different company anyway. WHAT YOU DO IS NOT ART OR SCIENCE - GET PAID.
Everything else in between: negotiable, especially as long as the dev is on the hook for initial support.
Until the second coming of whatever holy being you prefer occurs and he/she/they/it defines development practices in a miraculous manner there is going to be significant room for debate on any project not directly responsible for life and death decisions that isn't so insignificant to be disposable.
Everything outside of life-critical labeled best practices is usually more like company policy, client spec, or personal opinion. Many of them are personal opinion that many people currently agree on, but that does not make it an immutable guide for all situations.