←back to thread

Against Best Practices

(www.arp242.net)
279 points ingve | 2 comments | 18 Nov 24 07:45 UTC | HN request time: 0.435s | source
Show context
larsrc ◴[18 Nov 24 11:06 UTC] No.42171384[source]▶
Follow best practices unless you can give a reason not to. "Best practice" is a shorthand for a lot of accumulated knowledge that you don't want to go over again every time. Also following BP makes the code more consistent and thus easier to understand. But when an argument arises, go back to the underpinnings of the best practice and work from there.
replies(6): >>42171403 #>>42171433 #>>42171565 #>>42171805 #>>42171879 #>>42171960 #
1. davedx ◴[18 Nov 24 12:48 UTC] No.42171879[source]▶
What if the "best practice" was invented by a VC funded company (like, just for example, Vercel) desperate to maintain their growth trajectory by any means necessary, including huge marketing pushes to convince everybody the "best practice" is the "best way to do things"?

It's downright dangerous to assume a "best practice" in software development somehow automatically means it's some super distilled wisdom juice. A whole lot of it, in my experience, is just hype and rapid, unquestioning cargo culting slamming in right behind the hype.

Use your fucking brain. If the "best practice" is objectively a good solution to your problem then use it. If not, think of something better.

replies(1): >>42172024 #
2. bayindirh ◴[18 Nov 24 13:12 UTC] No.42172024[source]▶
I mean, consuming anything without vetting the source of the information is a bad practice in general.

...or,

The best practice of best practices is vetting the source of the best practice to verify its authenticity.

No?