
What happened
After a model shipped to production gave clearly wrong predictions within a week — caused by a mismatch between training-time and inference-time feature building — the author recommends three readable English MLOps books in order: Machine Learning Engineering with Python, Machine Learning in Production, and Machine Learning Pocket Reference, which together run just over 800 pages.
Why it matters
The books are presented as a path to the missing skill in such failures — designing the whole pipeline from training to serving as one system — which practical articles, in the author's account, cannot supply, and splitting the reading into finishable units lowers the chance of stalling partway.
Summaries like this, in your inbox every morning.
The author's own story sets the frame: a model that looked accurate in a notebook began producing clearly wrong predictions within a week of release, and the cause turned out to be a mismatch between how features were built during training and during inference. That is an engineering problem rather than a modeling one, and it is the gap the three books are meant to close. The stated method was to switch from thick standard volumes — repeatedly bought and left unread — to books of around 300 pages that could be finished and read in sequence in a short period.
Each book plays a different role. Andrew P. McMahon's Machine Learning Engineering with Python, written from the author's experience leading machine learning engineers in the UK, walks through requirements, training pipelines, packaging, deployment and monitoring using tools that appear in real work such as pytest, MLflow, Airflow and containers, and it also covers team structure and how projects are run. The Kelleher brothers' Machine Learning in Production starts from software engineering basics like version control, testing and algorithmic complexity, then moves through probability, statistics, regression and dimensionality reduction into designing data products. Matt Harrison's Machine Learning Pocket Reference narrows to structured data — missing values, feature creation, imbalanced data, model choice, evaluation metrics and feature importance — and is presented as something to open during work rather than read cover to cover.
The author's suggested progression is the three in order, which he says minimizes overlap, and he notes the combined length is about that of a single thick standard book. For anyone who has accumulated unread volumes, the argument is that splitting the material into finishable units makes it far less likely the reading stalls.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.