The line between software development and software architecture is a tricky one. Some people will tell you that it doesn't exist and that architecture is simply an extension of the design process undertaken by developers. Others will make out it's a massive gaping chasm that can only be crossed by lofty developers who believe you must always abstract your abstractions and not get bogged down by those pesky implementation details. As always, there's a pragmatic balance somewhere in the middle, but it does raise the interesting question of how you move from one to the other.
Join us for this tutorial where we look at the software architect role and how it should be a part of all software development teams. In summary, we will:
Simon Brown | 06 March 2012 | QCon London 2012 | London, England