Another older book I recently read; The Pragmatic Programmer was informative and is really a more detailed example go Agile software development than the Agile Manifesto, which the co-authors are also authors of.

I listened to the audiobook and I think the material would be better consumed as written word. The primary reason is that the book is organized by development activity and the most productive way to consume the book is probably to scan the topics and choose the ones you would like to go deeper on.

The book provides a set of principles for how to make development more iterative and scalable, but due to its broad approach can not offer specific actions to a developer. I think that is what the authors set out to do and is fine as long as the reader knows what they are getting. A productive use of the book would be to read the section(s) of interest and then dive deeper through more technical books and documentation to apply solutions to their specific use case.

Overall I would say the book is pretty good, and is worth a read for developers who find themselves getting stuck in rework or telling people about their programs rather than refining them or developing new ones. It is also very approachable as the tone is conversational and the authors intentionally leave space for the developer to apply their principles to resolve their challenge / opportunity.