The role of software architect has never really been clearly defined, and it means different things to a lot of people and at different companies. That leads to confusion over what is expected from architects and just practicing architecture. So I want to focus on the fundamental skills that are required to do architecture well. That's things like communication, decision making and leadership. If we understand those core fundamental skills, we can apply them to any situation that comes up and that leads to better software.

One thing I want to establish is that architecture is not only for architects. You don't have to have an architect's job title. I want to provide advice that anyone–from a developer to an architect–if you're working on software, I want them to get information that they can take back to improve how they design and build software. From small little decisions to big enterprise wide decisions.

I think seeing that software architecture is almost a team sport, that it takes a lot of people being involved. It's not just the one architect up in the ivory tower anymore. Then, because of all that interaction, you have to improve communication. That's a fundamental skill we always see on a job description, like “good written and oral communication skills.” That's really important, especially if you are going to be good at architecture and building good software.

The thing that I've been most surprised by, the sessions that have been about remote work. That was just before the pandemic in QCon London 2020, and there's been several after the pandemic when people were scattered, really. I always expect great technical presentations from QCon. Those talks that are more people-focused are some of the unexpected gems. So not just the hybrid remote work, but also things like the Staff+ engineer track, like how do you make yourself a better person in the software development community?