Simon Brown

Depending on your viewpoint, Simon is either a software architect who codes or a software developer who understands architecture. When he's not developing software with .NET or Java, Simon can usually be found consulting, coaching or training. Simon has also written books about Java, presented at industry events and has put together a training course called Software architecture for developers, which is based upon his software architecture writing at Coding the Architecture.

Twitter: @simonbrown
E-mail: simon.brown at codingthearchitecture.com

Recent Blog Entries
1	Software architecture: where do you start? You may have seen this on Matt Deacon's blog already ... I'm running a session for the IASA UK chapter on the 9th of March in London. Where do you start? One of the hardest things about software development is being asked to come up with a design ...	03-Feb-2010
2	The tension between software architects and their employers Sergey Mikhanov has written a blog entry called Why I don't believe in software architects that, along with the follow-up comments, makes for a good read. It discusses some of the ways that software architecture is typically viewed (e.g. models rather ...	27-Jan-2010
3	2009 highlights and plans for 2010 - part 4 Onwards then. The plan for 2010 is simple ... more content about pragmatic software architecture and more training. I particularly want to tackle the practical side of the software design process, including how to approach software design given a blank ...	08-Jan-2010
4	2009 highlights and plans for 2010 - part 3 My final highlight from 2009 is that we improved our Software Architecture for Developers training course by restructuring it and adding more content. We've run this course for several hundred people now and the feedback is consistently excellent. ...	07-Jan-2010
5	2009 highlights and plans for 2010 - part 2 In addition to the new content, 2009 saw us present at a number of conferences and events over the year, with all of the slides being able to download and view online. Here are some highlights. Documenting your software architecture - why and how?: ...	06-Jan-2010
6	2009 highlights and plans for 2010 - part 1 Happy new year all! Despite the financial climate, 2009 turned out to be a fairly busy year. The rationale behind Coding the Architecture is to be a useful resource for hands-on, pragmatic software architects written by people with the same background. ...	05-Jan-2010
7	December 2009 training summary I've had a few people ask me for a write-up of the recent training course, so I thought I'd put something together. This was the first time I've run the course with the new content and structure in place and the feedback was excellent. In the past, I ...	18-Dec-2009
8	You don't need a UML tool When tasked with the job of coming up with an architecture and design for a new software system, one of the first questions people ask is about which tool they should use. Such discussions usually focus around the Unified Modeling Language (UML) and ...	04-Dec-2009
9	Software architecture is a platform for conversation If you're writing software as a part of your day-to-day job, then it's likely that your software isn't going to live in isolation. We tend to feel safe in our little project teams, particularly when everybody knows each other and team spirits are high. ...	01-Dec-2009
10	Start with the big picture One of the hardest things about the software architecture role is being asked to come up with a software architecture when all you're given is a set of requirements and a blank piece of paper. It's certainly one of the most fun parts of the role, but it ...	18-Nov-2009