The essence of Clean Architecture would have fit nicely into a single, albeit maybe somewhat lengthy, blog post.
The filling material which makes up about 70-80% of the book, is also not per se of bad quality. It mostly reiterates rather basic concepts, but I'd qualify it, depending on the how experienced a reader is, as too shallow for an in-depth treatment or too bloated for a high-level overview. And the unavoidable morale tales from Bob Martins projects are also entertaining, but I personally don't seek entertainment in software engineering books.
I think, it can be worth skimming, but I don't consider it an essential read.
I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
The essence of Clean Architecture would have fit nicely into a single, albeit maybe somewhat lengthy, blog post.
The filling material which makes up about 70-80% of the book, is also not per se of bad quality. It mostly reiterates rather basic concepts, but I'd qualify it, depending on the how experienced a reader is, as too shallow for an in-depth treatment or too bloated for a high-level overview. And the unavoidable morale tales from Bob Martins projects are also entertaining, but I personally don't seek entertainment in software engineering books.
I think, it can be worth skimming, but I don't consider it an essential read.
Nice summary, Fabian.
I had the same idea about the book fitting into a long blog post but it didn't make it into the final version of my post.