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.
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.
Comments on this page are now closed.
©2017, O’Reilly UK Ltd • (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. • firstname.lastname@example.org