37 Things One Architect Knows About IT Transformation: A Chief Architect's Journey

The book provides practical and pragmatic advice from someone that has immersed themselves in the world of IT transformation. The call-outs regarding middle management as primary blockers of change, communication skills are key, and the importance of staffing core transformation teams with builders instead of enterprise architects, resonated with me. I also agree that IT advisors are first and foremost storytellers (that provide prescriptive guidance from lesson learned through their successes and failures), and too many vendor presentations lack pathos and ethos. The book was an enthralling read.

In my opinion, the author, as a good diagnostician, collects many facts linking the idea of ​​the disease with its symptoms, possible causes, previous events, its development and consequences, as well as ways to cure or alleviate it.Calling other people's mistakes is much easier and more enjoyable than recognizing your own.The book allows you to intelligently “gossip”, and this is a powerful incentive for serious self-criticism, and critical thinking workouts.Strongly recommended!

Every one of the things described in this book has made me think - "yes this is exactly how things are." This book is an excellent guide to an aspiring architect to know what to expect in the industry and how to work towards building successful projects.

A must read for all IT architects in this modern agile devops world. Gregor's use of metaphors to describe IT concepts is second to none, and this book is just packed cover-to-cover with real-world tips that will make you a better architect.

This is an amazing resource for people who want to gain experience quickly and learn valuable lessons about IT architecture.

It's a good read.

37 Things is one of the best books about software architecture I've ever read. In fact I read it twice; the first time even before it has been officially published. Here are some assorted reasons why it is definitely a must-read for each software developer who thinks about moving to the architect role, as well as for each architect.The book is full of humor and literally makes you LoL every now and then. A great example is the term "Feet of Enterprise Architecture". Try guessing that does it denote? The humor makes it very east to ingest and internalize the knowledge which this book is full of.Great analogies. Analogies are good when trying to explain something but software industry is cursed with bad and horrible analogies. The ones Gregor uses are supreme. Example? Comparing architect role to movie characters. Yes, you'll find Matrix there.Deep insights. Many people use the building architecture -- IT architecture parallel but Gregor actually cares to tear this analogy apart and put it back again to show what a good architecture document should and (more importantly) should not contain.Invaluable are parts dealing with leadership, decision making and systems thinking.Once caveat though: before you open the book prepare to change most of your current opinions on the software architecture. You have been warned!

Ce livre n'est qu'un condensé de lieux communs, de dictons que vous connaissez déjà ou de conseils bateaux.L'auteur ne fait que lister des conseils ultra vagues sur quelques lignes et puis passe à un autre sujet.Très déçu d'avoir suivi les autres avis sur ce livre.Si vous avez déjà une petite expérience dans un SI d'une grande boite, même sans être architecte, vous connaissez déjà absolument tout ce qui est dans le livre.

This book was really a revelation: it was like someone reading my mind and explaining to myself my own thoughts with much greater insight and wisdom. "Yes it's exactly like that". This book contains all the possible answers you may be looking for while navigating the perils of modern IT transformations, and even the questions you did not know how to ask. A must-read.

Gregor Hohpes neues Buch "37 Things One Architect Knows About IT Transformation" ist kein klassisches Software- oder Enterprise-Architektur Lehrbuch welches den Leser von der Pike auf in das Thema einführt. Im Gegensatz zu den klassischen Fachbüchern wagt der Autor in den einzelnen Kapiteln häufig den Blick über den Tellerrand. So geht es zwar auch um zahlreiche technische Themen aber der Autor versteht es, die Rolle des Architekten realistisch in seiner Gänze zur portraitieren. Ich fand insbesondere die Abhandlungen zu Kommunikation mit Stakeholdern, Organisationen und die eigentliche Rolle des Architekten sehr lesenswert und erfrischend. Denn: als Architekt hat man nicht nur mit Patterns, Bebauungsmustern, Architekturmustern oder Technologien zu tun sondern eben auch mit zahlreichen Stakeholdern auf verschiedensten Ebenen der Hierarchie einer Organisation.Das Buch liest sich kurzweilig, ist zu keiner Zeit trocken und der Autor versteht es sich als unaufdringlicher aber aufmerksamer und vor allem kompetenter Beobachter in den Hintergrund zu platzieren. Ein tolles Buch, welches ich jedem Software Architekten und vor allen denen, die gerade aus der Software Entwicklung in diese Rolle hineinwachsen, wärmstens empfehlen kann.

Thanks

Same verbatim text as his "Architects Rlevator" which is good and I have, however I bought this expecting something different, its not.