summaryrefslogtreecommitdiff
path: root/technical
diff options
context:
space:
mode:
authorKévin Le Gouguec <kevin.legouguec@gmail.com>2018-06-15 15:52:04 +0200
committerKévin Le Gouguec <kevin.legouguec@gmail.com>2018-06-15 15:54:26 +0200
commit206bcc6142d9c1a26ccc0f26c6da730f8f1fd3b0 (patch)
tree3b939944466db1b502b0aef6c2a611f59af39c98 /technical
parent0a1bf29ee247ce33b72f54d5b10327b89051799b (diff)
downloadmemory-leaks-206bcc6142d9c1a26ccc0f26c6da730f8f1fd3b0.tar.xz
Start the blog roll
Aka "bookmarks with misguided commenraty".
Diffstat (limited to 'technical')
-rw-r--r--technical/blog-roll.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/technical/blog-roll.md b/technical/blog-roll.md
new file mode 100644
index 0000000..6dd8849
--- /dev/null
+++ b/technical/blog-roll.md
@@ -0,0 +1,20 @@
+This is a list of blog-ish websites where I found insightful stuff
+that I would like not to forget.
+
+# LispCast
+
+Eric Normand's musings on programming paradigms and their application,
+with a soft spot for functional programming.
+
+[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
+ express that paradigm?", we often reduce the question to "does
+ this language possess those features?".
+
+ Normand wonders whether we do this because the procedural
+ paradigm's metaphor (a series of steps that each may contain any
+ number of sub-tasks) maps so well to its features (sequential
+ statements, subroutines) that it trained us to mix those up.
+
+[Programming Paradigms and the Procedural Paradox]: https://lispcast.com/procedural-paradox/