Back on

WordPress MoveAfter ten days of blogging on, here I am, back on It’s a decision made with both hope and regret, but one that I need to make in order to continue the work I started.

Over the past three years on, my ability to write code (PHP and JavaScript in particular) had degraded quite a bit. I had thought that by self-hosting my blog, I’d be more motivated to try new things, and force myself to learn as I inevitably broke things on my own blog. It turns out that such a tactic had the opposite effect. I had every intention to break things and learn, with daily plans even, but I was too timid to put my rusty skills to the test on a live blog.

Considering that, my main blog is now back on, but I’m keeping a few self-hosted test blogs around so I can break things and learn without fear. I still learned quite a bit in just ten days, like how to have a similar setup to, working with caching, choosing a stats program, and how to work with Genericons (which you can do on with certain themes). I even helped fix two bugs in the Authy plugin.

As for the rest of you still on, if you use Jetpack, I submitted a few bug reports and feature requests you might like. One of those might even be my first patch one of these days.

18 responses to “Back on”

  1. Be brave, put your main blog on a self hosted server and test the hell out of it with dodgy code and mad ideas. It’s what I do! πŸ™‚

    • Genericon’d is awesome! I went ahead without it as it had been bugging me that I couldn’t quite figure it out. Now that I have, I have a lovely Genericon “Follow Elsewhere” widget in my widgets area above, since we can’t exactly use Genericon’d here.

      When I’m ready to go again, I’ll take you up on that offer to help break it, but you might regret it. πŸ˜‰

  2. Welcome back to the fold. πŸ™‚ I also set myself a goal this year of becoming more familiar again with WP standalone. Regretfully, it’s not been easy to follow through on as I’d thought. (Tried to leave the comment on G+ but it wouldn’t post, dangit.)