Coding the Architecture
The new name for The Pragmatic Architect
I'm pleased to announce "Coding the Architecture", the new name for "The Pragmatic Architect". Since this site started we've covered a wide range of topics, from the role of an architect and software development methods through to Java and SOA.
For me, the new name says something that the old one didn't and it fits in really well with much of the content that we've already published on the site. Coding the Architecture reflects...
- That the architect should (or at least be able) to get involved with the hands-on coding activities.
- That delivering an executable reference architecture (or vertical stripes, spikes, etc) is essential for proving the architecture and justifying the non-functional requirements.
- That coding the architecture is more important that simply documenting it, particularly in the fast moving, deadline-driven world that we live in.
- That the code *is* the architecture.
- That all of the contributors code on a regular basis yet we still find ourselves in architect or architectural roles.
All of the thepragmaticarchitect.com URLs will continue to work and you can remain subscribed to the existing RSS feed or use the new RSS URL. Either way, you'll get the same content and existing links will continue to work. Stay tuned, we have some interesting new content up our sleeves...
Re: Coding the Architecture
Re: Coding the Architecture
I'm sorry, but I have to agree. 'Pragmatic' meant something to me, it meant hands-on, it meant... well... pragmatic.
'Coding the Architecture' to me means a blog for people who think that architecture isn't 'real' unless you can write code.
There seems to be a misconception that 'technical' and 'hands-on' means 'writes code', which I resent to be honest!
Tom
Re: Coding the Architecture











