←back to thread

Against Best Practices

(www.arp242.net)
279 points ingve | 4 comments | 18 Nov 24 07:45 UTC | HN request time: 0.001s | source
Show context
eapriv ◴[18 Nov 24 12:17 UTC] No.42171733[source]▶
Software around us is quite terrible, so it’s kind of obvious that one shouldn’t follow “best practices” that led to this state of things.
replies(2): >>42171758 #>>42172915 #
1. rileymat2 ◴[18 Nov 24 12:22 UTC] No.42171758[source]▶
That implies they were created with best practices in the first place.
replies(2): >>42171942 #>>42173789 #
2. resonious ◴[18 Nov 24 12:59 UTC] No.42171942[source]▶
If not, then what was created with best practices in the first place?

If we can agree that most large, financially successful software projects are of questionable quality, then either

- they used best practices and yet they still suck, OR

- they did not use best practices, but are widely successful anyway.

So no matter how you look at it, software best practices just haven't panned out.

replies(1): >>42197910 #
3. eapriv ◴[18 Nov 24 16:14 UTC] No.42173789[source]▶
The name “best practices” kind of implies that they actually are practiced somewhere. So it’s different from theoretical abstract ideas “how we should write software”, which maybe nobody follows.
4. a96 ◴[20 Nov 24 20:43 UTC] No.42197910[source]▶
"All hardware sucks, all software sucks."