Re:Famous Laws of Software Development (2017)
by BerislavLopac on Monday February 25, 2019 @09:19AM
(#19245739)
Or Greenspun's Tenth Rule of Programming:
[ Parent
| on HN ]
Re:Famous Laws of Software Development (2017)
by neilk on Monday February 25, 2019 @12:32PM
(#19247437)
I encountered a literal version of this the other day.
I’ve been looking at some disused AI systems, which were all written in Lisp back in the day.
In an attempt to remain relevant, at one point in the early 2000s someone tried porting one of them to Java. By first writing a Lisp interpreter in early 2000s Java. So the system had all the old dynamic Lisp programs as giant strings, embedded in a fugly static class hierarchy.
Re:Famous Laws of Software Development (2017)
by tabtab on Monday February 25, 2019 @11:46AM
(#19246871)
A mutant variation of this: Greencodd's Rule: "Every sufficiently complex application/language/tool will either have to use a database or reinvent one the hard way." (from c2.com)
Re:Famous Laws of Software Development (2017)
by flambard on Monday February 25, 2019 @03:57PM
(#19249398)
And then there is Virding's First Rule of Programming:
Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang.
Re:Famous Laws of Software Development (2017)
by tabtab on Monday February 25, 2019 @11:49AM
(#19246904)
Variation 2: If you factor duplication heavily and go ultra-meta, you'll end up with Lisp or a clone of Lisp. However, only Lisps fans will be able to understand the code.