Nope. Right there at the beginning is where the author goes off track.
Computation itself is the most important aspect of computing. Code and data are just complexity to manage.
> Do I have a Customer? It goes into class Customer. Do I have a rendering context? It goes into class RenderingContext.
I whole heartedly agree with this. The naive approach to domain modelling is to classify the primitives of a domain into classes and stop there. In actuality, the processor of those primitives is likely what your class should be, and those primitives ought to be methodless data structures.
I.e., OrderFulfiller instead of Customer and Part classes.