←back to thread

Against Best Practices

(www.arp242.net)
279 points ingve | 6 comments | | HN request time: 0.207s | source | bottom
1. eapriv ◴[] 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 #
2. rileymat2 ◴[] No.42171758[source]
That implies they were created with best practices in the first place.
replies(2): >>42171942 #>>42173789 #
3. resonious ◴[] 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 #
4. NathanaelRea ◴[] No.42172915[source]
Maybe if people didn't follow best practices their software would be terrible-er? Guardrails for hard things doesn't imply no guardrails would make it easier.
5. eapriv ◴[] 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.
6. a96 ◴[] No.42197910{3}[source]
"All hardware sucks, all software sucks."