InfoQ Homepage Presentations The Frustrated Architect
The Frustrated Architect
Summary
Simon Brown discusses the role of the software architect, challenging some of the current assumptions and trying to redefine it in the context of Agile development.
Bio
Simon Brown is an independent consultant based in Jersey, 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 .NET and Java platforms, Simon now uses his experience to train and coach teams in delivering better software.
About the conference
GOTO Aarhus is the enterprise software development conference designed for team leads, architects, and project management and is organized by developers, for developers. As software developers and architects ourselves, we wanted to craft the ultimate conference. The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community, staged in an intimate environment needed to support as much learning and networking as possible.http://gotocon.com/
Community comments
Superb Presentation
by Chandermani Arora,
One Architect v.s. Many Architects
by Marco Ramirez,
The Frustrated Former Software Engineer
by Johnny FromCanada,
Superb Presentation
by Chandermani Arora,
Your message is awaiting moderation. Thank you for participating in the discussion.
This was a really awesome presentation Simon! Really thought provoking. Incidentally i to posted some rants about Architect with resonates with some of your thoughts. See my post chandermani.blogspot.in/2012/04/architect-give-...
One Architect v.s. Many Architects
by Marco Ramirez,
Your message is awaiting moderation. Thank you for participating in the discussion.
Good Presentation.
The conference mentions the explicit case where there is a single architect in a project, and suggest to migrate to explicitly developers sharing the architecture role.
But, it didn't mention that , in real world, many projects, doesn't have an explicit architect, and instead, implicitly every programmer performs its own architecture.
A plus for mentioning the "shinning new toy sindrome".
The Frustrated Former Software Engineer
by Johnny FromCanada,
Your message is awaiting moderation. Thank you for participating in the discussion.
Is it just me, or should all this be blatantly obvious for any self-respecting software engineer worth their salt? What the heck are universities teaching these days? The right answer is always "it depends". Or is the tech industry so hurting for lack of software coders, that anyone who has read a book can get a job. Now that's frustrating!
Regardless, I suspect that within 10 years software architecture will be relegated to the now emerging platforms-as-a-service, and mobile OS's. Abstractions are becoming more "first class" by the day. But for now, I suppose it makes sense to bring these issues to light as a counter-revolutionary buffer/reminder against uncontained Agile revolution.