I read from the 1974 Turing Award Lecture by Don Knuth.

Thoughts on Functional Programming Podcast by Eric Normand

Computer Programming as an Art

We read and discuss the 1973 ACM Turing Award Lecture by Charles W. Bachman.

Programmer as Navigator

We read from and comment on Edsger Dijkstra's 1972 Turing Award Lecture called The Humble Programmer. Is the problem with programming that we don't recognize our own limitations? We'll explore that and more.

The Humble Programmer

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.

What's the relationship between abstraction and generality?

In this episode, we explore why Clojure's stance of not wrapping data much is so powerful in the world we live in.

Why is data so powerful?

In this episode, I read from and discuss a comment thread between Rich Hickey and Alan Kay.

What if data is a really bad idea?

In this episode, I read from David Parnas's important paper on modularity.

On the criteria to be used in decomposing systems into modules

In this episode, I explore the notion of fit and how it is missing from the Stratified Design paper.

What is missing from Stratified Design?

In this episode, I read and comment on excerpts from John McCarthy's 1971 Turing Award Lecture.

Generality in Artificial Intelligence

In this episode, I read and comment on an excerpt from the 1970 Turing Award Lecture by James Wilkinson.

Some Comments from a Numerial Analyst

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).

Don't overcomplicate the onion architecture

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.

Is Haskell the best procedural language?

Force is an important concept in Newtonian mechanics. But do forces really exist? In fact, it is an abstraction invented by Newton. The insight revolutionized physics and universalized his model. What can we learn from it?

Do forces really exist?

One of the greatest domain models ever built was Newtonian mechanics. Why did it take physics, as a field, thousands of years to figure it out? What can we learn from Newtonian mechanics to help us model our own domains?

Could we build Newtonian mechanics on purpose?

We discuss two phases of domain modeling, one easy and one difficult. https://lispcast.com/how-is-domain-modeling-related-to-starbucks/

How is domain modeling related to Starbucks?

An off-the-cuff stream of Functional Programming ideas, skills, patterns, and news from Functional Programming expert Eric Normand.

hubhopper

Thoughts on Functional Programming Podcast by Eric Normand

hubhopper