Igor

I had never studied systems analysis before the course. Almost all of the techniques turned out to be new for me. These 5 weeks were one of the most knowledge-saturated in my life.

For example, before this course I theoretically understood that technical decisions should be based on reality. However, I couldn't tell which exact features influenced the final choice, and how. The main insight of the course was the systematization of that comprehension. Now it's much easier to find better solutions and justify them in front of the team.

The course will benefit not only architects and engineers with ambitions to be analysts, but also all the developers who want to find good technical solutions.

Andrew

I chose this course because I was familiar with Anton's work and had already taken his course about asynchronous architecture. I had a feeling (and it proved to be true) that the course would be high-quality and straight to the point. Practical tasks to consolidate the material were a great bonus and additional motivation!

During the course I grasped what Event storming is and how to apply it. And most important — I gained practical experience! I figured out how to justify the choice of an architectural solution for the project in general and its individual services.

Daniel

The main benefit of the course is the clear understanding of how to approach complex systems. The process looks more predictable now, and I have instruments to deal with each step of it. I feel more confident in my decisions.

In my work tasks I try to use event storming and stakeholder map / concerns, to evaluate architectural characteristics and choose a solution based on them.

I recommend this course to engineers starting from mid-level.

Dmitry

I had a chance to try a bit of ES, but I probably won't carry it through. The work plans for this project have changed, and for the current one ES is redundant =)

All of the materials were very useful: event storming, allocation of root domains, data models, dealing with requirements, working with stakeholders, creating architecture plans. I actually can't choose the one most valuable thing from the course. I was used to doing things by guess, as I thought fit, but the course has given me a whole picture that now helps me complete tasks better. I will still need some time to process all the new knowledge.

I would recommend this course to anybody who's interested in designing systems. Even if you don't want to get the position of an architect, you will still learn to speak the same language with architects and ask the stakeholders the right questions.

Dmitry

I first took the demo version of the course and thought "that's an interesting course about practical architecture". I expected to get some new knowledge that would balance the business vs development relationship.

Now I've got the practical skills of designing systems without thinking too much about the technical realization. The thing from the course I've already started doing in my work project is dividing domains according to business logic.

Nick

Turning almost every homework into an event storming model was a very useful task. That's a great chance to revise the information and understand how to do everything better.

I can recommend this course to everybody whose job is connected to designing systems or to any related stages of creating the architecture of complex systems. This course will help you understand what happens on the phase of designing architecture and stop viewing that process as a black box that creates difficulties for the sake of difficulties and work for the sake of work.

Dmitry

I wish this course was taught at universities. I would've developed much faster and made fewer mistakes. I've been interested in architecture for a long time. I've read "Clean Architecture" by Martin, as well as DDD-books (green and blue). But when I tried to implement the knowledge from the books, I kept coming up with the same nonsense. I wanted to fix it and start thinking differently. This course has helped me a lot.