Tim Gittos

I'm an Australian currently living in Austin, TX in the USA.

I currently earn a living programming, though I wouldn't call myself a programmer. If I had to attach a label to myself, I'd use the term autodidact.

I love learning, and my favorite things to learn about are programming, computer graphics, AI & machine learning, robotics, painting and creativity.

Now On Jekyll

Last updated on 27 May 2011

I first started my blog in order to help myself learn. I figured that I would be motivated to write, and in order to fully explain things, I would force myself to do research and increase my knowledge on a given topic. So I set up a Wordpress blog, created a very simple theme and got started with it.

This was all good in theory, but in practice it didn’t quite work. This really bugged me, because I didn’t know why it didn’t work. I thought about it for a long time, and I think I’ve figured it out.

The reason it wasn’t working is because the way I think and do things is very different from the workflow of Wordpress. Wordpress is a very linear blogging system. Posts are displayed in the order they’re created, and if you want to do a series of detailed posts in multiple posts, you either need to do them one after the other, or you need to keep them as drafts until they’re all done.

I tend to work a little different. I like to do a lot of things at once, and nibble away at posts. I’ll write a little here and a little there, and generally take my time to produce content. This wasn’t working for me in Wordpress, and it was actually starting to make me feel bad.

So, I decided to change to a platform that’s a little more freestyle. I chose Jekyll because I decided to integrate my site with Github. Now I don’t have to worry about logging in to a web based control panel, because everything is handled with public/private key encryptions on Github, and it’s very easy to deploy to my sever with a post-commit hook that tells my server to do a git pull.

I’m also writing in textile now, which means that should I produce any content that’s worth publishing, converting it to TeX then to a PDF or something similar should be equally easy.

This is probably time for the obligatory “this is a work in progress” comment, and to say that things will be in flux for a while, at least until I get settled on a format/workflow that really works for me. I’ve been working with this for a while now offline, and it seems to be doing the trick, but there are still a few bugs to iron out.

You can also find all of my old posts still on the website, in my archives , however I couldn’t bring across all the comments, so to those of you who commented on my writing, thank you and I’m sorry.