Software architecture is very simple: You only have to split up one system and use modern approaches such as DDD or Microservices. This presentation shows completely different qualifications that a good software architect must have.
The focus is on the technical decisions that an architect has to make, how to best deal with such decisions and how to find out on what basis decisions can be made. And because software projects always take place in a team, soft skills and teamwork are also important.
What will the audience learn from this talk?
A lot about social skills to become a great architect and even some concrete techniques.
Does it feature code examples and/or live coding?
Prerequisite attendee experience level: