This was of the most interesting sessions I attended in a while. Knowing a bit about software architecture, I tried to learn more about main principles of software architecture and this session truly delivered.
Very educational session for developer, BA, QA, PM or Architect who wants to know more about the general principles of software architecture. And for me which little knowledge in this area, I was amused to learn and also see how some of these principles can be applied to many other areas even everyday life situations.
So is an architect?
- Investigator
- Butcher
- Tactician
- Judge
- Instructor
- Entrepreneur
An architect defines the problem and analyses the risk
An architect splits/partitions the problem into smaller discrete pieces.
An architect makes plans according to the big picture and assigns responsibilities.
An architect needs to understand trade-offs and make trade-offs on quality attributes.
An architect needs to grow architectural capabilities of others.
An architect needs to balance the risk and manage the technical debt.
