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.
James Thompson is a principal software engineer at Mavenlink, where he is committed to helping engineering teams become more deliberate in how they build software through developing strong learning cultures, principled engineering practices, and holistic architectural thinking. He has worked with web technologies since 2003.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com