The Future of Rinsefirst

Over the last few years, I’ve become more and more of the belief that the best solution isn’t always do it yourself. Do it yourself generally means a lot of work, and to make it compatible to something else out there, might take a lot more work.

Take for example this blog.

For the last few years, it has gone from being a:

• Static html website – It was black, and was known as JJ’s Domain at the time.
• PHP Template Site – It was white with boxes, had the ISMS, still known as JJ’s Domain
• A Oxwaf CMS Site – It looked like a washing machine.
• A Sunfox CMS Site – Your looking at it.

There were a few other design changes in there, but basically that’s the history of the code as it was.

The truth is though, I haven’t had “all” of the features I’ve ever wanted in a blog. In fact, every time I’ve switched code, I’ve lost functionality because I didn’t want to take the time to re-create it.

Now the benefit here is, I’ve been able to do what I want, when I want, how I want. But I code every day now… I’m writing much more advanced applications with much more specific purposes. The functionality features of *my* personal blog, rarely interest me. So much so, that I’m writing this post in phpMyAdmin, not even in my own editor. I just don’t have the time to waste to improve this site except when I want to test a feature of sorts.

That said, I’m strongly considering migrating this site to WordPress. I recently migrated BananaMonkey.com to it, and must admit, I like the flexibility of it all. It’s fast, has modules that I can plunk in, and it just works… The only reason I can think not to switch is because it’s my code… But really, once you know you can write it (and you still have the ability to change anything you want), why not right?

So who knows… maybe I’ll be on WordPress myself after tonight…