I'm kinda sad "databases" got excluded. On the one hand, I get excluding SQL & ACID; but B-trees I'm disappointed to see not make the main list¹. They're such a fundamental datastructure, and I continue to run into programmers who do not understand how a B-tree works. (E.g., that it is inherently ordered/sorted, and what sort of operations it makes fast. I'm willing to lower the bar so that "how it works" isn't required.) But I think there's a lot of practical stuff in relational algebra, too: in particular, the notion of a "key" — I also find programmers who do not understand this — and the various normal forms and why you want them. Practically speaking, I think something like 99% of engineers are going to touch these topics in a "a user of them" sense.

While I wouldn't include ACID either I think, but I think you do want something like this: https://jepsen.io/consistency — then you can talk about it when you have to work with aaS cloud systems don't obey anything on that list, at all.

Also I think you're going to have to work to convince people that floating point was a good idea. (I agree, but I doubt that agreement is universal.)

(¹I know it's like on a "good ideas" sublist in the excluded section. But it's such a good idea I'd've pulled it out to the main list.)