Some might ask why a guy who loves his life of code would choose WordPress as the framework for one of his websites. Well, I chose a WordPress blog. I almost didn’t. It’s been a long time coming. It’s early in the game, but I think it was a good choice.

Why I wouldn’t choose WordPress blog

I only had one job about 7 years back that consisted of mostly PHP. The job was great for many reasons. PHP wasn’t the highlight. We did some cool stuff with it. At the time, it was all right. Since, I have coded full time in Java, Python, XQuery, or JavaScript. I would count each as more enjoyable than PHP.

Secondly, I’m a coder. I love to build stuff. Custom software is way more fun than boxed software. WordPress is something that is literally accessible to anyone that’s just computer savvy. I’m not breaking new ground on WordPress.

An insightful article

A week or so ago, I ran into an article on a site called “Virtuous Code”. That site name was cool enough. The article was typed (“penned” is such a cooler word) by Avdi Grimm and is named “Why WordPress”. I was caught off guard by how well it described my personal predicament.

Why I chose a WordPress blog

When I read Avid’s article, I realized that the reasons I, as a coder, had been avoiding WordPress were the very reasons I should embrace it:

  1. As a coder, my tendency to jump into the internals and start toying around is strong. This hinders my writing ability. It competes for my time. Writing is something that I really want to do more of. By choosing a package that’s tied up with a bow will encourage me to just use it instead of over-customize it. And since the innards of the package is a language that I don’t want to devote a ton of my time to, I’m even less inclined to customize it.
  2. PHP and WordPress are, in a way, like JavaScript – they’re everwhere, and everyone is using them. This means that probably just about everything that I could imagine wanting (ok, I’ll probably come up with something innane) on a blog has already been built. I don’t need to reinvent it.

Driven to the edge

So, I made the jump. I just downloaded the latest package. I ran Apache on my local box and pointed my browser to localhost:8888. I was presented with the pleasant admin UI. I chose a new theme. It installed in place. It was a 2-click ordeal. I chose a few plugins to replace default functionality and add a bit more. I was pleasantly surprised by the smoothness of it all.

At the point I was getting the blog looking nice and doing what I wanted, did I care that the thing was written in PHP? No. I saw it just once when setting up my DB connection. I did cringe slightly upon seeing some super globals again ($_SERVER), but I hastily committed the change and deployed the app.

We’ll see if I continue to love it, but so far, so good. My fellow coders, I ask: Is my reasoning sound?