memory-leaks

Still reachable: lots of words in many pages.
git clone https://git.kevinlegouguec.net/memory-leaks
Log | Files | Refs | README | LICENSE

commit 206bcc6142d9c1a26ccc0f26c6da730f8f1fd3b0
parent 0a1bf29ee247ce33b72f54d5b10327b89051799b
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Fri, 15 Jun 2018 15:52:04 +0200

Start the blog roll

Aka "bookmarks with misguided commenraty".

Diffstat:
MREADME.md | 2+-
Atechnical/blog-roll.md | 20++++++++++++++++++++
2 files changed, 21 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md @@ -1,5 +1,5 @@ # Peniblec's Memory Leaks -## still reachable: 3492 words in 5 pages +## still reachable: 3619 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 @@ -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/