not that interesting to read and it feels very "purist" , in the sense that it doesnt seem to acknowledge how to balance refactoring with other code changes. im guessing the legacy code book in this series is more focused on that. but it felt v annoying to read like "keep everything up to date always clean everything u touch" when thats not possible in a huge codebase. 

its also VERY java specific in some chapters, and OOP oriented when its not java oriented. in the age of web development, this isnt as useful for everyone depending on your tech stack

however, the actual principles discussed are great and have changed how i write and review code. but like there are articles that summarize these points just as well, it isnt that helpful to read the entire book