Re:Low Hanging Fruit of Programming Language Design
by jonahx on Wednesday November 22, 2017 @01:54PM
(#15759391)
It's a great principle and I reference it frequently, but as a catchy buzzphrase it has the potential to do as much harm as good: it's easy to abuse as an excuse for copy paste programming.
Duplication is still bad, and correct abstractions are still good.
Re:Low Hanging Fruit of Programming Language Design
by djur on Wednesday November 22, 2017 @02:27PM
(#15759682)
See also "premature optimization is the root of all evil", which I occasionally see stretched to include any kind of thinking about the performance characteristics of your code, even down to basic design decisions like data structures or algorithms.
Re:Low Hanging Fruit of Programming Language Design
by grandalf on Wednesday November 22, 2017 @05:19PM
(#15761187)
Great point. I've found that most codebases have some abstractions that work very well and others that work less well, and simply having awareness of this can help make the code far more readable.
For instance, one might say: "The way x is implemented works, but it's not quite the right abstraction, here's why". That is way more informative than saying it's simply the wrong abstraction or considering it good enough and ignoring its deficiencies.
This needs to be given a catchy phrasing and spread all across developer communities!
WTD == Worse Than Duplication?
WAAW == Wrong Abstractions Are Worse?