- True best practices mainly refer to standards, and this list is very slowly updated, unlike the number of false ones;
- It's often used for marketing purposes, which works well, but doesn't always imply quality;
- Since this spreads fast, we often have things at the places where they do not fit, but squeezed into, because it's the best, so we must have it;
- Forms a wrong mindset to rely upon someone else's experience instead of learning and gaining own understanding.
In the end, we have tons of inapplicable or controversial information to filter, which doesn't make things better, in my opinion. Sharing is great but we should do it responsibly.
It's also a bit funny to watch how the best practices suddenly become the worst.
Edit: formatting
#1) The value of any practice depends on its context.
#2) There are good practices in context, but there are no best practices.
[1] https://www.softwaretestinghelp.com/what-is-context-driven-t...
But I do agree, the hype of the day isn't a best practice either. And just the term "best practice" without any qualifier or context is already a sign of incompetence.
The tech and terminology often dazzles less savvy businesses and they're happy until problems start to arise.
"Best practices" almost always come out of some business or project explaining what tested best with their circumstances. That alone tells you everything you need to know. Invest in a testing process which exposes the most critical parts of your application/infrastructure, attempt to overwhelm or exploit them, and you'll find out what your best practices need to be real quick. Those best practices may work at other companies but not nearly as well as if they invested in their own testing processes that are as or more rigorous than yours.