Technical debt is a metaphor used to explain the tradeoff we all face when we have a deadline. How much is it worth to rush the code out the door? It’s a good metaphor, but the term is often used these days to mean ‘code I don’t like’. In this episode, I examine the parts of the metaphor and ways in which technical debt differs from financial debt.
Thoughts on Functional Programming Podcast
An off-the-cuff stream of Functional Programming ideas, skills, patterns, and news from Functional Programming expert Eric Normand.
I explore why clean code is a lagging indicator and how the domain model is a leading indicator of maintenance cost.
I begin exploring the process of domain modeling with a definition.
I read from the 1974 Turing Award Lecture by Don Knuth.
We read and discuss the 1973 ACM Turing Award Lecture by Charles W. Bachman.
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.
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.
In this episode, we explore why Clojure’s stance of not wrapping data much is so powerful in the world we live in.
In this episode, I read from and discuss a comment thread between Rich Hickey and Alan Kay.