Yesterday, on the recording of the book "Software Architecture: The Hard Parts", we recalled the book "Building Evolutionary Architecture". ("Evolutionary architecture").

And I decided to remember her here today. This book is good if you read it in the original language. I once talked about the basic concepts at a conference and wrote an article called "Evolutionary Architecture in Practice." https://apolomodov.medium.com/evolutionary-architecture-introduction-a06cfd4b9aa5 For those who are interested in reading/seeing there, here I will criticize the standard translation of the publishing house Peter:

It seems that the Russian version was obtained with the help of Google Translate, because in the book there are banal problems with the fact that many places are translated simply into the forehead, for example: development and operations in the context of interaction between departments, guys lead as development and operations. For example, development can write code, and operations can lay it out:))) There are microservice areas and microservice reporting, for domain microservice and report microservice:) You know, microservice area, BL... area:)) When we talk about feature toggles, this is called switching functions for system functions:)) Further, the combination of possible positions of these toggls is called permutations, which is simply wrong from the point of view of combinatorics, where it is clearly stated what permutations, combinations, etc. are.

In general, the Russian version of this book is just a terrible thrash. You can only read to those who

• is a mazachist. He does not speak English and speaks well in the subject.
• a person who will help the publisher to work on the errors and to the second edition to translate this good English book normally into Russian By the way, the authors of the book have problems, because they do not know what is directly proportional and inversely proportional dependence:) Specifically, this manifests itself when they write that speed is directly proportional to the iteration time:) Speed is directly proportional to time. And the team of authors consists of 2 technical directors and chief technical consultant thoughtworks:)

P.S. The worst thing about this book is that it’s really good... but only in the original English version, and the Russian edition is money for the wind.

#SoftwareArchitecture #Architecture #SystemDesign