Take a photo of a barcode or cover
51 reviews for:
Clean Architecture: A Craftsman's Guide to Software Structure and Design
Robert C. Martin
3.99 AVERAGE
51 reviews for:
Clean Architecture: A Craftsman's Guide to Software Structure and Design
Robert C. Martin
3.99 AVERAGE
A bit hard to get through even though the writing is quite light-hearted and entertaining in general. I mainly got confused about all of the acronyms and also the diagrams varied in understandability. But I did find myself thinking "Ooh that makes sense, I wish I had known that earlier!" numerous times while reading this book. Finally, my advice is to read this in long sessions and as short a time period as possible, because I did find that to be more effective than going weeks without reading, and then trying to get back into it.
challenging
informative
inspiring
lighthearted
reflective
fast-paced
challenging
informative
medium-paced
A pretty excellent book. I was afraid that this would simply be full of patterns to memorize but interestingly enough, it's not very detailed. Or rather it's not concerned with details but rather with the concepts.
And what are these concepts? Martin thinks this can be summarized into one sentence. "The goal of software architecture is to minimize the human resources required to build and maintain the required system". Simple as that. And the principles that will get you there are simply the SOLID principles which can be found anywhere on the internet.
What's really remarkable is that the SOLID principles were some that I heard when I started working in software engineering 6 years ago, and they still feel like some secret superweapon that I can use today. Even crazier is that these principles have existed for a long time and we don't seem to have found better principles to ensure great architecture.
When it comes to software engineering books I'm mostly interested in the books that are timeless. Clean architecture is one of them, and in the fast moving field of software engineering, that should speak volumes to its quality.
And what are these concepts? Martin thinks this can be summarized into one sentence. "The goal of software architecture is to minimize the human resources required to build and maintain the required system". Simple as that. And the principles that will get you there are simply the SOLID principles which can be found anywhere on the internet.
What's really remarkable is that the SOLID principles were some that I heard when I started working in software engineering 6 years ago, and they still feel like some secret superweapon that I can use today. Even crazier is that these principles have existed for a long time and we don't seem to have found better principles to ensure great architecture.
When it comes to software engineering books I'm mostly interested in the books that are timeless. Clean architecture is one of them, and in the fast moving field of software engineering, that should speak volumes to its quality.
As a simple programmer this was a bit beyond me. I found everything about it confusing from the acronyms to the directions of arrows in all the diagrams.
informative
reflective
slow-paced
As my rating says: I liked it (no more, no less) :-)
It has not become one of the main technical books that I would recommend to someone, and I don't feel that there are no "new ideas", but I found it useful as a reminder of many concepts.
It has not become one of the main technical books that I would recommend to someone, and I don't feel that there are no "new ideas", but I found it useful as a reminder of many concepts.
informative
medium-paced
medium-paced
informative
medium-paced
Una lectura obligada para todos los desarrolladores de software interesados en hacer mejor software.
Si quiere ser arquitecto, este libro contiene todos los conceptos básicos intrinsecos en cada patrón de arquitectura que está de moda, hoy son microservicios, ayer era SOA, mañana serán nanoservicios pero siempre el propósito será el mismo que se describe, con gran habilidad, en este libro: desacoplar componentes, trazar dependencias, identificar detalles y separarlos del dominio.
Si quiere ser arquitecto, este libro contiene todos los conceptos básicos intrinsecos en cada patrón de arquitectura que está de moda, hoy son microservicios, ayer era SOA, mañana serán nanoservicios pero siempre el propósito será el mismo que se describe, con gran habilidad, en este libro: desacoplar componentes, trazar dependencias, identificar detalles y separarlos del dominio.