One of the several websites I follow regularly is that of my friend Bryan, and as a result was introduced to Dean Barker. I really enjoyed reading through Dean's archives, especially since the site layout made it so easy, but one passage really got my attention.

I challenge you to pick one system, live with its flaws, celebrate its strengths, but more or less forget about the technical and architectural end of it and instead concentrate on the user at the other end of the keyboard. Focus on delivering him or her actual content. (You remember, the reason we install these system in the first place?)

This one paragraph does well to sum up my theory regarding web apps. Read the rest of Dean's post to get the drift as I am tempted by the plagiarism demons to copy the entire post just for my own future reference. As for myself, I have chosen Drupal as the object of my attention. I would love to tell you right now that Drupal has no flaws and limitations and readily accepts wharever concept I throw out there and automagically creates a taxonomic workflow complete with menu structure and a tag cloud to boot. In reality, I alter the classic question of "Can Drupal do this" to "How can Drupal do this" with each new challenge I face. Perhaps Drupal is not the best solution for everything, but it is the solution I have chosen. By familiarizing myself with it's nuances I keep Drupal as the default solution for all diverse projects.

In the not for small minds to ponder department, the question is raised: "Is your CMS truly able to handle all that you throw at it, or do you subconsciously alter your vision in such a way that your CMS can handle?" Do we really care, as long as it works?

Like me, Dean Barker recognises the power of Movable Type and it's ability to stretch to fit your needs. Movable Type is very very nice, but I drink a new coolaid now. We must learn and move on.