Beyond accidental architecture

In many cases, existing architectures represent an accident of circumstances. James Thompson explains why you should move beyond the accidental and introduce intentional architectural thinking to your team, outlining the benefits of deliberate software architecture, from helping newer engineers understand why certain boundaries exist to enabling senior engineers to improve their skills and more.

In many cases, existing architectures represent an accident of circumstances—big balls of mud that grow naturally anywhere there is a lack of deliberate architectural thinking and practice. James Thompson explains why you should move beyond the accidental and introduce intentional architectural thinking to your team, outlining the benefits of deliberate software architecture, from helping newer engineers understand why certain boundaries exist to enabling senior engineers to improve their skills and more. Emphasis will be given to how to implement many of the suggestions in a variety of team contexts and how to seek to turn skeptics into advocates. You’ll leave with a number of practical ways to help your teams overcome accidental architecture. Topics include: