Software Architecture and Web 2.0ness

        I was talking with a coworker the other day (Squid) about various architecture stuff. For those who are not in “the know”, software architecture is just the way of organizing large software projects into more manageable chunks. For those kind of in “the know”, go read “Don’t Let Architecture Astronauts Scare You” . Basically as you get more experience in how software projects get put together someone will decide your an “Architect” now and not just a developer. This means you spend more time playing with onmigraffle and keynote then you do with make and gcc. Anyhow Squid was asking me about my new found attempts to maintain a blog and how he felt a blog compared to a wiki. I had just introduced Squid to wiki’s a few weeks earlier and he was really getting into them while he viewed a blog just a diary and not really a way of organizing information like what can be achieved in a wiki. It was at this point in the conversation that I slapped on my marketing/architect hat and said “That is the great thing about the web paradigm, you can have a wiki and a blog and have links that go between them allowing to cross reference the information in each, either the blog or the wiki and let each provide the information in the way that is most natural. That way your not trying to shoehorn information into a blog that best represented in a wiki and your not creating a bunch of wiki pages that should really be a blog. It is the intersection of having information, representing the information in the most natural way, and cross linking so it can be found in multiple ways.”

        I then came out of my trance, the aliens left my body and asked Squid what had just happened. He said you just made a lot of sense and if you need to capture that exact thought you just had in your blog......So Squid, this one’s for you.