Evolutional design

Has it ever happened that you saw (someone else's) code and wanted to rewrite everything? Has it ever happened that you could not understand why someone took a specific decision, not another? Would you like to exclaim: "I could make it so much better!"?

If you ever thought about it, you will be interested to hear the story of how these issues arose in Alexandr and Kirill practice, and how they were solved in a big company.

Developers will tell how in the beginning of the road they pulled checkers and went on the attack in troubled architecture. But it was not so easy, and as the guys dive into the project they began to realize that a large system architecture is a compromise between different approaches and solutions, innovation and legacy (inherited code), centralization and decentralization of components. Speakers have gained a lot of experience in solving architectural problems and will share their experiences and develop principles that are held by them at this time.

During the session, difficult questions will be discussed arising from decisions on how the system will live and evolve.

Together with students, Alexander and Kirill will do exercise to create a "tech table" and its evolution. They also will show the importance of engineering solution at any stage of system development.