Some things I don't want to learn

I can’t usually tell people what I do at work. This is largely because I don’t think that what I do is very easy to classify; half the time I’m not even sure what I’m doing.

Between what I do to pay the bills (Blog Business Summit) and what I do for fun to try to pay the bills (Flicker Gaming), I end up spending a lot of time doing things that I never thought I’d know how to do in the first place.

When I first bought the Flicker Gaming domain, I had no idea how to install a CMS of any kind, not even a blog. I hired a friend to install e107 and tweak it so I liked how it looked. It worked OK, but I’m a control freak and I like to keep tweaking things, and that wasn’t really going to work for both of us, so I set out to teach myself Wordpress.

I think I’ve done a decent job. Decent enough that I get paid at work to develop sites in Wordpress, and that’s pretty impressive.

But as I keep going I find that the things I end up doing are getting ever more technical. I look at sites like Mike Davidson’s blog and I realize that there’s a certain level of complexity I don’t think I ever really want to understand.

I’m far more interested with the superficial tweaks, and frankly, I’d rather come up with an image file and have someone else do all the crazy coding that needs to happen behind it.

At the same time, every step of the way I see things that look hopelessly complex, and then three months later I’m actually trying to do them. I never wanted to be a crazy techie webmaster, but I keep finding myself further down that road.

I just hope I keep doing other stuff as well. Eventually, I’d like to hand off the webmaster work at Flicker to someone who really knows what they’re doing, and move to blogging and, for lack of a better term, managing things. But that’s gotta wait until we have revenue.