Code of Architecture: Building Evolutionary Architectures

We had it yesterday. fifth and final stream We have mentioned the following books and concepts:

• "Software Architecture Metrics: Case Studies to Improve the Quality of Your ArchitectureA book with examples of architectural metrics 10 software experts
• Whitepaper "From X programming to the X organisationAuthored by Enrico Zaninotto - an article from the conference, where the design was looked at from the point of view of the design of the organization
• "Organization: A Tool for Software Architects • Eberhard Wolff • GOTO 2021" - a speech on a similar topic, namely that the organization is a tool for the work of architects Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations is a book about building high-performance organizations that popularize DORA metrics. (deployment frequency, lead time for changes, mean time to recover, change failure rate). It is a must read for technical managers, although there is a reasonable criticism research (as usual in studies about the possibility of correlations to draw causal conclusions)
• Review of the book "Learning DDD"- We've already discussed it in the Code of Architecture club and I made a brief recap. In this book, many topics are considered much better and deeper than in evolutionary architecture.
• The book.Continuous Architecture in PracticeAnother book about the continuous development of systems architecture, which I found to be an order of magnitude better than evolutionary architecture.
• The book.Project Phoenix. (The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win)The book is written in the genre of a production novel and is similar to the book "The Purpose" ("Goal") or Critical Chain. ("Critical Chain") Goldratta. However, here the main actions take place not in the factory, but in the habitat of it’s employees of Parts Unlimited.
• "Unicorn Project (The Unicorn Project: A Novel about Developers, Digital Disruption, and Thriving in the Age of Data)This book was written by Gene Kim as a continuation of the previous book, The Phoenix Project. (The Phoenix Project)" The last book showed the impact of managers on development processes, and this book shows the impact of individual contributors.
• Jeff Bezos letter to Amazon shareholders 2015 year Here he talked, among other things, about Invention Machine and solutions of two types: -- Type 1 - "Some decisions are consequential and irreversible or nearly irreversible – one-way doors – and these decisions must be made methodically, carefully, slowly, with great deliberation and consultation" -- Type 2 - "But most decisions aren’t like that – they are changeable, reversible – they’re two-way doors. If you’ve made a suboptimal Type 2 decision, you don’t have to live with the consequences for that long." In fact, this letter was about being able to make decisions. 2 quick, and solutions like 1 methodically and carefully. Gradi Booch’s definition for Software Architecture is “Architecture represents the significant design decisions that shape a system, where significant is measured by cost of change.” But now they often offer irreversible decisions to postpone until the moment when we have enough information and the decisions themselves can not be made. This provides some flexibility to the architecture and suitability for further evolution.

Perhaps the list of materials can end here. It should also be noted that the book ended and it was not as interesting as I personally expected ... but in communicating with the guests, we pulled out a lot of ideas that made discussing this book much more useful than just reading it. In the last issue, we were helped by Sergey Baranov, the organizer and creator of the ArchDays conference, as well as the author of Agile Mindset and the Telegram channel. Microservices are a Russian-speaking community.

#SoftwareArchitecture #Architect #CoA