Strategy, discovery, metrics, growth, pricing, design, delivery and leadership. Each entry says when it is the right one to pick up.
Kalbag covers the ground a team needs in order to start taking accessibility seriously, from the legal and business context through to specific implementation guidance.
Humble and Farley's book on getting software from commit to production reliably. Covers the deployment pipeline in detail, build and dependency management, the testing strategy across levels, configuration management, managing …
Kleppmann covers the foundations beneath data systems. Part one covers reliability, scalability and maintainability, data models and query languages, storage engines and encoding.
Huyen treats machine learning as a production systems problem, covering everything around the model rather than the modelling itself. The book moves from framing a business problem as a machine learning problem and deciding …
Reis and Housley describe the data engineering lifecycle, which runs from generation through ingestion, storage, transformation and serving, with governance, security and architecture cutting across all of it.
An attempt to give software architecture a shared foundation rather than leaving it to war stories. The first part covers architectural thinking, modularity, and the architecture characteristics a system is actually being optimised for, along with how to identify and measure them.
A beginner's guide to SQL built around real public datasets rather than toy tables. It starts with creating and querying tables, then works through joins, aggregation, subqueries, common table expressions and window functions using census, taxi trip and food inspection data.
Google's account of how it runs production systems, written by the engineers who do it. The central ideas are the service level objective as an explicit reliability target and the error budget that follows from it, which turns …
Google's account of the practices that let thousands of engineers work in one codebase over decades, organised around culture, processes and tools. The opening argument is that software engineering is programming integrated over …
Adzic's book on specification by example, sometimes published as Bridging the Communication Gap. Covers deriving scope from goals, specifying collaboratively, illustrating requirements with concrete examples, refining those into a …
A plain language guide to the technology behind software products, written for people who need to hold their end of a conversation with engineers. Covers how the internet works, software development, operating systems, databases, hardware, security and business models.
Lauret writes about API design from the consumer's point of view, treating an API as a user interface for developers. The book starts by identifying the goals an API needs to support, then covers designing the resources, actions …
The practical companion to The Phoenix Project, organised around the three ways of flow, feedback and continual learning. The flow section covers deployment pipelines, automated testing, low risk release patterns and the architecture that lets teams deploy independently of each other.
Burkov compresses the field into a book you can read in a weekend, with the mathematics present but held to what is genuinely needed. It covers supervised learning from linear and logistic regression through decision trees …
The companion volume to Site Reliability Engineering, written to answer the question of how to put the ideas into practice. Where the first book describes how Google runs production, this one gives worked examples of service level …