Two books across thirty days. One per fifteen days. Both are O'Reilly, both are standard references, and both are books that people buy and never open.

The point of putting them on a schedule is that a schedule gets read and a wishlist does not.

Days Dates Book Author Why it is here
Days 1 to 15 Sep 28 to Oct 12 Designing Machine Learning Systems Chip Huyen The book that treats ML as a systems problem rather than a modelling problem. It is the closest thing to a textbook for what you are doing in Weeks 1 to 3.
Days 16 to 30 Oct 13 to Oct 27 Designing Data-Intensive Applications Martin Kleppmann The reason your Week 4 system design does not fall apart under questioning. Consistency, partitioning, replication, failure. None of it is AI-specific and all of it is required.

The reading pace

Neither book is meant to be finished in fifteen days. That is not the goal.

Read one chapter every two or three days, alongside the builds. Roughly 20 to 30 pages a sitting. When a chapter connects to something you built that week, note the connection in your repo. That note is what you will actually remember.

Kleppmann in particular is dense. Chapters 1, 3, 5, 6 and 9 carry most of what you need for the Day 28 Capstone. If you only read five chapters, read those five.

Neither book is required to complete Build30

Every build, problem and live session works without them. Nobody checks.

They are here because the gap between an engineer who has read Kleppmann and one who has not becomes obvious around minute twelve of a system design interview, and because thirty days is a good window to start something you will finish over the next six months.

Buying them

Both are available directly from O'Reilly and through the usual retailers. Both have India editions at India pricing. If cost is the blocker, say so in Discord and we will sort it out.