Modeling of problems is something that feels like a lost art. And completely a subtext in so much of what programmers discuss.

What I mean by subtext is that OO is a way to model a problem as much as it is a way to organize code. Same for what we often call functional. Yet we spend far more time and effort talking only about what it means to organize the code, with kind of a byline on how it helps to model the solution.

I do think it is there, but by the time you show someone how a SAT solver is just working on the true/false of various variables, and that it often can be seen as "learning" combinations of those variables that are known true/false, that is so far away from the typical understanding of the problem that it looks alien.