How not to ruin the architecture right away? Video from the lecture of Evgeny Krivosheev

Hello!

Two weeks ago, another CodeFreeze meeting took place in Moscow. Our guest was Evgeny Krivosheev , a recognized Russian expert in the field of software architecture, a consultant from Scrumtrek / Skilltrek. Eugene gave an awesome lecture on architecture , how he loves and knows how.


')
In the framework of this meeting, Eugene suggested discussing the sequence of solutions that are critical for the architecture of any system . The earned sequence of actions is as follows:

• Points of view on the system, or Why we are going blind in the design
• Addressing key risks, or Pride kills
• We take into account the context, or How not to peck at the closed door

What was discussed at the last meeting:

• What is architecture?
• How to describe it?
• How not to go blind: Points Of View
• The scale of modern systems
• What is more important - database schema or concurrency design?
• Embrace the immensity: "Elephant" and "Hypercube"
• Architectural frameworks - 4 + 1, Rozansky & Woods, Zachman
• See quality behind the charts - examples with three charts
• Kill Pride: Addressing Risk
• Case with a library
• Design as recursive contracts
• Architecture as the most risky contracts
• Prototyping
• External examination
• Turning on common sense: what to consider when designing
• Formal design approach kills: Arch = F (?)

And here is the video:



Be sure to watch the video if you are interested in any of the issues raised above.

PS: we thank our sponsor, OK.ru, and Deutsche Bank, which provided the premises and helped with the organization of the meeting.