7 thoughts on “Why You Hate Your CMS”

  1. Your argument, quite articulate and well reasoned, gives credence to the notion of object-oriented methods and patterning in software development – the growing need to retain a handle on data structure without sacrificing manipulability. The consequences are increasingly slower code (hence the need for faster machines) albeit with greater functionality (how high can high-level programming languages go?). Perhaps it’s time for computer scientists to come up with abstractions that lend themselves well to both needs: preservation of structure and functional flexibility.

  2. Nice. I’m reminded of the observation that practicing gynaecology is akin to trying to paint a hallway through the letterbox; managing content through a CMS seems at least partly analogous.

    1. Hi Chris. Thanks for the comment. That is a great metaphor! I agree it seems apt. Sometimes it is not only the size of the data set that is the problem, but the angles from which you can reach it.

      1. Absolutely. Had a nice moment of this the other day, when we took a bunch of website abstractions and functional requirements off the computer and organised it all over the wall. Went from “gah, I can’t apprehend this” to “I see exactly how this all fits together” in about two hours.

        1. Yes, it’s great when you can do that. Beyond a certain scale of data, however, it is impossible to spread it out on the wall. There is just too much. It is then that you need to turn to analytic techniques to query, summarize, and re-order the data so that you can comprehend it.

          This is where content management systems tend to fall down. They contain too much data to comprehend by simply viewing it spread out, but they don’t make the data accessible enough to apply effective analytic techniques to it.

Leave a Reply

Your email address will not be published. Required fields are marked *