Beyond accidental architecture
Accidental architecture is a product of circumstances rather than deliberate development toward a goal. James Thompson explains why it's best addressed by equipping teams to make more deliberate and informed technical decisions.
|Talk Title||Beyond accidental architecture|
|Speakers||James Thompson (Mavenlink)|
|Conf Tag||Build resilient systems at scale|
|Location||New York, New York|
|Date||September 20-22, 2016|
Deliberate software architecture provides numerous benefits to teams, from helping newer engineers understand why certain boundaries exist to helping more senior engineers grow their architectural skills. Yet in many contexts, the architectures that exist represent an accident of circumstances. Join James Thompson to move beyond the accidental and introduce intentional architectural thinking to your team. Accidental architectures exist throughout the world of software. Big balls of mud grow naturally anywhere there is a lack of deliberate architectural thinking and practice. James details ways for technical leaders within a team to introduce deliberate architectural thinking and process to environments where architecture by accident already exists. Topics include: