There should come a time when every programmer is developing and then has to stop and ask himself/herself: "Why am I using such a complicated library to do a simple thing. Is Javascript really that hard?" And the answer should always be the same, probably not, but doing it right is really hard because faster is easy and easy is easy... and I like being a whore.

Earlier today Ryan Bates posted an interesting article on how people abuse Ruby modules and how those modules can create badly managed code by decoupling the context too much. It was a real good read and it's words hold true for quite a few programmers. Me included probably... This article got me thinking about some of my own nitpicks on modules and classes, and while completely unrelated I figured I would document them because they fall along the lines of what I consider abuse.

Yesterday, a client; after having told him a month before that he needed more content to draw users in, came to me asking about blogging software, after me having stripped out all the capability that was this because it was "too much" in their eyes and I was overstepping my boundaries le sigh. Somebody had recommended that they start a blog and I'm not going to dispute this guys opinion, it's right. All things that ran through my head when he said that (pretaining to the aforementioned situation,) aside I started to think to myself, how do I select a system when I'm looking for something to power my sites.