commit 74d228b3970bb2b08c21c6fe9f179e2ec3e5f17f
parent 206bcc6142d9c1a26ccc0f26c6da730f8f1fd3b0
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date: Fri, 15 Jun 2018 16:57:09 +0200
Add another LispCast article
Diffstat:
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
# Peniblec's Memory Leaks
-## still reachable: 3619 words in 6 pages
+## still reachable: 3717 words in 6 pages
Hi! I am a software engineer interested in [a bunch of things].
diff --git a/technical/blog-roll.md b/technical/blog-roll.md
@@ -6,6 +6,21 @@ that I would like not to forget.
Eric Normand's musings on programming paradigms and their application,
with a soft spot for functional programming.
+[When in doubt, refactor at the bottom] (2017)
+: Quoting Sandi Metz:
+
+ > Duplication is far cheaper than the wrong abstraction.
+
+ The point being that blindly following the letter of the DRY law
+ can lead developers to add complexity to extracted functions
+ because "it almost does what I want; if I could add just one more
+ parameter to it…".
+
+ Normand and Metz encourage developers to "mechanically" extract
+ small pieces of logic; even if they are not re-usable, bundling
+ things together and naming them helps make the potential
+ abstractions more visible.
+
[Programming Paradigms and the Procedural Paradox] (2017)
: A discussion on our tendency to conflate *paradigms* with their
*features*; for example, when trying to answer "can this language
@@ -17,4 +32,5 @@ with a soft spot for functional programming.
number of sub-tasks) maps so well to its features (sequential
statements, subroutines) that it trained us to mix those up.
+[When in doubt, refactor at the bottom]: https://lispcast.com/refactor-bottom/
[Programming Paradigms and the Procedural Paradox]: https://lispcast.com/procedural-paradox/
