Do abstract and general mean the same thing? I don’t think so. I’ve actually stopped using the term ‘abstraction’ because it’s so laden with semantic baggage. We explore what they do mean in different contexts, and why abstract is not a relative term.
Thoughts on Functional Programming Podcast
An off-the-cuff stream of Functional Programming ideas, skills, patterns, and news from Functional Programming expert Eric Normand.
Subscribe on iTunes, Google Play Music, Overcast, or via RSS.
Why is data so powerful?
In this episode, we explore why Clojure’s stance of not wrapping data much is so powerful in the world we live in.
What if data is a really bad idea?
In this episode, I read from and discuss a comment thread between Rich Hickey and Alan Kay.
On the criteria to be used in decomposing systems into modules
In this episode, I read from David Parnas’s important paper on modularity.
What is missing from Stratified Design?
In this episode, I explore the notion of fit and how it is missing from the Stratified Design paper.
Generality in Artificial Intelligence
In this episode, I read and comment on excerpts from John McCarthy’s 1971 Turing Award Lecture.
Some Comments from a Numerical Analyst
In this episode, I read and comment on an excerpt from the 1970 Turing Award Lecture by James Wilkinson.
Don’t overcomplicate the onion architecture
When using the onion architecture, you need to consider the dependencies (actions depend on calculations), but also you need to consider the semantic dependencies (the domain should not know about the database).
Is Haskell the best procedural language?
Functional programming is a mindset that distinguishes actions, calculations, and data. That’s where it derives its power. Simply applying the discipline of ‘only pure functions’ lets you programming using a procedural mindset and still think you’re doing functional programming.