←back to thread

Against Best Practices

(www.arp242.net)
279 points ingve | 1 comments | 18 Nov 24 07:45 UTC | HN request time: 0.207s | 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 #
ohthatsnotright ◴[18 Nov 24 11:17 UTC] No.42171433[source]▶
Often what is one developers "best practice" is another's "anti-pattern" because a lot of this is just arbitrary.
replies(4): >>42171555 #>>42171558 #>>42171648 #>>42171680 #
1. pydry ◴[18 Nov 24 11:57 UTC] No.42171648[source]▶
There are many like that. Every practice is a trade off.

However, there are many where the cost/benefit ratio is so large that you can default to "you should just do this".

I dont think Id ever look at a company that e.g. had no CI or versioning for a large project for instance and think "they might have had a good reason for this". They didnt.