Software architecture plays a pivotal role in the delivery of successful software yet it’s frustratingly neglected by many teams. Whether performed by one person or shared amongst the team, the architecture role exists on even the most agile of teams yet the balance of up front and evolutionary thinking often reflects aspiration rather than reality.
If we really do want to succeed, we need to get over our fascination with shiny new things and starting asking some questions. Does agile need architecture or does architecture actually need agile? Have we forgotten more about good software design than we’ve learnt in recent years? Is emergent design really just about foolishly hoping for the best? Does any of this matter if we’re not fostering the software architects of tomorrow? How do we move from frustration to serenity?
Jersey, UK
Simon lives in Jersey and is an independent consultant, the founder of Coding the Architecture and either a software architect who codes or a software developer who understands architecture. Having successfully delivered a variety of projects on the Microsoft .NET and Java platforms, Simon now also regularly speaks to and teaches audiences across Europe about software architecture and its role in modern software development teams. He is also the author of a “Software Architecture for Developers” book, which is being published incrementally through Leanpub. He still writes code too.