I explore a new perspective about what abstraction means and how it can cause problems.

Why does some design advice work for some people, but not for others? And why do some agile practices work for some people, but not for others? I call that The Christopher Alexander Effect and explain how it works.

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.

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.