I read this book to get up to speed with modern software data engineering. I think I achived the goal, although I finished with a knowledge of how much I do not know, rather than with the confidence in building the solutions myself.
James seems to take an opinionated approach by using cloud warehouse databases (Redshift and Snowflake). The use cases and computations are well suited to them, and I would need to read other recourses to see how the patterns mentioned play with other technologies. The price/ops complexity of possible stacks is not mentioned.
The chapters with SQL examples look great. I learned a bunch there.
There are also enough mentions of various technologies and books throughout the book -- I learned about Kimball modeling, dbt, Airflow, Atlas...
It would be great to extend the reasoning about production and operations, pitfalls and risks -- such as schema migration, scaling, schema registry, deployment, versioning, durability risks, retention, backups, recomputing... Validation, metrics collection, and slack notifications are presented and I would like to hear more about some visualization.
Overall it is a good book and I only wish every chapter of it would be bigger. Oh wait, there is "Pocket" in the name. Nevermind, then.