I found that learning good programing principles from this book was even more useful than learning the design patterns it describes. Besides amazing content, it's wonderfully fun to read as well.

This is so far my favorite book and the one I come back to the most. It covers programming paradigms, SOLID principles, components, and then dives deep into software architecture.

A very fun and exciting novel about the woes of maintaining software infrastructure and deployment pipelines and schedules. I can't count how many times I laughed out loud when the protagonists had the exact same problem as we did in our everyday work. Learn together with them how to overcome these problems and get a fun introduction to DevOps culture.

Very similar in style, and just as fun as its predecessor The Phoenix Project, but focuses more on a single team, and software development, rather on bigger picture things. You could say that it's a zoomed in version of The Phoenix Project.

Ever wondered what technical or management practices actually produce quality, faster delivery and happier teams? Look no further. This book summarizes years of rigorous research from State of DevOps Reports, built upon 23,000 datasets from companies around the world. An absolute must read, regardless of whether you're a developer, manager or CTO.

This book introduced me to Conway's law and cognitive load. It discussed how and when to provide an organizational structure that matches the software architecture, and keeps the teams happy and productive. A tough read, but well worth the invested time.

I find Lean methodology extremely appealing and try to incorporate it whenever and wherever I can. This book discusses what exactly is efficient and what is wasteful. It's surprisingly insightful for such a light read.

It's easy, as a developer, to forget that your job is to make money for the company you're working for, by providing services that their customers delight in. Sometimes this is done by withholding from writing any code or even deleting some. This book discusses what an MVP can be, as well as the only metrics that actually measure how good your software is - metrics of the bottom line. It's so good I read it twice already.

I'm really inspired by the idea that the language of the domain experts should drive the development process. This is the core concept of Domain Driven Design.

A practical guide to implementing organizational efficiency through DevOps principles. It follows and expands on 'the three ways' in The Phoenix Project novel.