This post originated from an RSS feed registered with Java Buzz
by Simon Brown.
Original Post: Do you need a Java architect?
Feed Title: Simon Brown's weblog
Feed URL: http://www.simongbrown.com/blog/feed.xml?flavor=rss20&category=java
Feed Description: My thoughts on Java, software development and technology.
I've organised a couple of unconference sessions in London over the next few weeks, with the purpose of discussing what it means to be an architect on a Java project. Doing such a session in a traditional presentation style wasn't really an option because there are very few right or wrong answers when you start talking about this stuff. Instead, I want to us (myself and some of the other architects I work with) to share our own *experiences* of doing this type of work in the city.
Having worked with and coached aspiring architects, it's clear to me that many people see the role as a mystical thing that they don't know how to get to. So on the one hand, I want to demystify exactly what I think it means to be an architect. Having said this, I also want to share my experiences about some of the complexities and responsibilities of the role, because they help ensure the success of the project and its chosen architecture.
There's no set agenda for these sessions but I'm hoping that people want to talk about a mix of the technical and non-technical aspects of being an architect. I'm really looking forward to it and if you're looking at a career in software architecture (particularly with a Java focus), I recommend that you come along. Full details can be found at The Pragmatic Architect sessions in London. If you can't make either of these but are interested in us running another session (either publically or privately, inside your company), please do get in touch.