summaryrefslogtreecommitdiff
path: root/technical
diff options
context:
space:
mode:
authorKévin Le Gouguec <kevin.legouguec@gmail.com>2018-07-05 22:43:07 +0200
committerKévin Le Gouguec <kevin.legouguec@gmail.com>2018-07-05 22:43:07 +0200
commit45917933036cb0d672788c3ff8e8508f2c115508 (patch)
treee5df8c16c159eb9e3f70f2f6124c410191c2de16 /technical
parentc28de7d0cab86d8584377e33ceaa6b039ee16cf5 (diff)
downloadmemory-leaks-45917933036cb0d672788c3ff8e8508f2c115508.tar.xz
Tweak notes on LispCast
- link to the archive - drop the dates; too annoying to manage manually
Diffstat (limited to 'technical')
-rw-r--r--technical/blog-roll.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/technical/blog-roll.md b/technical/blog-roll.md
index efd3762..a624f57 100644
--- a/technical/blog-roll.md
+++ b/technical/blog-roll.md
@@ -1,12 +1,12 @@
This is a list of blog-ish websites where I found insightful stuff
that I would like not to forget.
-# LispCast
+# [LispCast]
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)
+[When in doubt, refactor at the bottom]
: Quoting Sandi Metz:
> Duplication is far cheaper than the wrong abstraction.
@@ -21,7 +21,7 @@ with a soft spot for functional programming.
things together and naming them helps make the potential
abstractions more visible.
-[Programming Paradigms and the Procedural Paradox] (2017)
+[Programming Paradigms and the Procedural Paradox]
: A discussion on our tendency to conflate *paradigms* with their
*features*; for example, when trying to answer "can this language
express that paradigm?", we often reduce the question to "does
@@ -32,5 +32,6 @@ 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.
+[LispCast]: https://lispcast.com/category/writing/
[When in doubt, refactor at the bottom]: https://lispcast.com/refactor-bottom/
[Programming Paradigms and the Procedural Paradox]: https://lispcast.com/procedural-paradox/