Kent Beck presents some of the concepts discussed in this book in his conference talk: A Daily Practice of Empirical Software Design (Domain-Driven Design Europe 2023)
I was a bit underwhelmed by the content until part 3 where he delves into the theoretical grounds for planning "tidyings". He leans on economics to discuss when the best time is for making a refactoring. I find making that connection valuable. But the way concepts are explained are not very clear, in my opinion. I didn't think of this book as "well-written" in general. And despite the claims in the beginning of the book, I don't think a senior engineer has much to learn from it (not from the first two parts, anyway). Perhaps, part 3 should have been a separate book. That would be an interesting read with clearer and more detailed explanations, some anecdotes and examples.