GOTO is a vendor independent international software development conference with more that 90 top speaker and 1300 attendees. The conference cover topics such as .Net, Java, Open Source, Agile, Architecture and Design, Web, Cloud, New Languages and Processes

Simon Brown, Coding the Architecture

Simon Brown

Biography: Simon Brown

Simon lives in Jersey (Channel Islands) and works as an independent consultant, specialising in software architecture and its role in modern software development teams. Simon regularly speaks at international software development conferences and provides consulting/training to software teams at organisations across Europe, ranging from small startups through to global blue chip companies. He is the author of Software Architecture for Developers, an e-book that is being published incrementally through Leanpub. He still likes to write code too.

Twitter: @simonbrown

Presentation: Sustainable competence - the people vs process and technology

Track: It's All About The People, Stupid / Time: Wednesday 11:30 - 12:20 / Location: Effectenbeurszaal

The budget has been secured and a team of software developers that know the latest in cutting edge technology has been hired. According to what you'll hear from the evangelists, it's a simple matter of letting the developers self-organise and the software will be ready before you can say "minimum viable product". Back to the real world and if it really was that easy you probably wouldn't be attending this conference. So why are some software teams really successful while others are less than stellar? Well it really is all about the people, stupid. In this talk I'll share some stories from my experience of working with a number of software development teams. Some of those teams were great … and then there were the others. Prepare to be horrified and amused in equal measure. Continuous improvement is only achievable if you have sustainable competence!

Workshop: Effective Architecture Sketches

Track: Training / Time: Thursday 09:00 - 16:00 / Location: Mendes DaCosta Kamer

The code might be the architecture but at some point in time you're going to have to explain how it works, and that's when the whiteboard pens make an appearance. Where do you start though? UML or block diagrams? How much detail should you include? Technology decisions included or omitted?

Agility is about moving fast and this requires good communication, but it's surprising that many teams find it tricky to effectively communicate the architecture of their software. In this tutorial you'll be asked to design a software system and practice communicating your vision through a series of simple yet effective architecture sketches.