Just another tech blog – ranting since 2006

Skills-based Resumes

I have recently been updating and freshening up my resume, and thought I would do something different… something to stand out. Having interviewed many people, from software engineers to product managers and CTOs, I have had the opportunity to see many resumes. Most of the resumes I see are quite bland and boring – as if written for a machine. They have no personality, no passion and no creativity. I wanted my resume to have personality, passion and creativity.

Since I am a well rounded engineer, I thought I would be able to cover more of my skills in a skills-based resume, instead of a chronological list of my work experience. I went through and split my skills into areas (Coding, Data, Operations, Communication, etc) and listed a few points under each. At the end, I added my work experience, but only with a short paragraph of what I did there.

While I thought this style made a good resume, recruiters hate it, and so do people trying to hire.

After getting some advice, I wanted to share it with the rest of the world. Here are the things people want to see in software engineering/technical resume:

  • Technical Skills: After your object at the top (if you want to display passion), make a clear section describing your technical skills – languages, databases, environments.
  • Summary: Recruiters give your resumes only seconds when determining its fit for a role, so help them out by having a small summary easily telling the reader how many years of experience you have, your last role, and perhaps your education. From this, they can deduce.
  • Accomplishments: When you do list the companies you have worked for, make sure to include some of your notable accomplishments and things you are proud of. If possible, try and quantify them (revenue generated, queries per second, amount of data).
  • Your Role: Let the reader know what your role and responsibilities were at each position you have held

Resume writing is a complex task, and something a lot of people dread. I have definitely not covered everything, but I did want to make clear a skills resume is not a good idea. Also be aware that many recruiting companies load resumes through a computer before even looking at them. Try to have keywords a search engine could pick up on (like SEO for resumes).

Perhaps resumes written for machines is a good thing after all?

Unlock your T-Mobile G1

I have successfully unlocked my T-Mobile G1 for free? How you ask? After 90-days, T-Mobile allows you to unlock almost any phone you have purchased from them with the T-Mobile branding, and all for FREE. The process can take about 2 weeks (as it did for me), but it worked. Here is how:

Call T-Mobile on 1-877-453-1304 from another phone (not your G1). I got that number from their Contact page Its the standard voice prompt thing, so say English, enter your G1’s phone number, then when they ask what you want help with, say the magic word “Agent” Then they ask what you would like to talk about, and say “SIM Unlock Request” My experience with T-Mobile has been pretty good, within a minute I was talking to the real person. At this point, you verify your identity, and explain to them you want to unlock you phone because you are going overseas and want to use another SIM card. They will ask you for you phone’s IMEI number. This is a sacred number, so be careful who you give it to, as you can report the phone stolen, give them the IMEI number, and have the phone permanently disabled. You will find the number: on the side of the box your phone came in, on the G1 itself under Settings –> About phone –> Status, or by dialing *#06# Give them your email address, and within 14-days, you will get an email from T-Mobile with your unlock code. To unlock the phone, power it off, insert a non-t-mobile SIM card, and power it back on At the prompt, enter the unlock code from the email and you’re done! The reason for writing this post is I had no idea this could be done for free with any T-Mobile phone after 90-days has past. There is no need to pay $25 to any scam site, just do it legit, for free, and without issue.

Django and Google App Engine Tutorial

Hi have been playing around with Google App Engine for a while now, and wanted to learn Django on a new application I am building. The two articles I started with are:

Both Django and GAE are being developed as I write this, so although these instructions are kind of recent, they are already out of date, or rely on you having knowledge of Django. Since there are a lot of others with no Python or Django experince wanting to learn, I thought I would make a tutorial that works as of today, but who knows a month from now or even tomorrow.

Note: This tutorial is written for Linux. Mac/Windows users will have to translate :–)


Django comes as a .tar.gz file, but we want a zip file to take advantage of the Zipimport library, so some conversion is needed.

  1. Download the latest Django and untar the file (in this case, it is 1.0.2)
  2. cd Django-1.0.2-final
  3. Create the zip file, but without the admin section since App Enging supplies it’s own zip -r ~/ django -x 'django/contrib/admin*'

Get the Helper

The App Engine Helper or Django is an open source bootstrapper for getting Django started on App Engine. Downloading it from the website will currently give you quite an old version (r52) which will not work in this tutorial. Instead, use subversion to get the latest (r74).

cd ~
svn export gae-django-tutorial
cd gae-django-tutorial
mv ~/ .

Setup App Engine

As you would with any GAE application, edit the app.yaml file to refer to your application ID. The Helper also needs to know where your Google App Engine SDK is, since it is going to change how you start the development server, so create a link to it:

cd gae-django-tutorial
ln -s /path/to/google_appengine .google_appengine

Start the development server

Django has a different way of running the development server. Instead of using to start the dev server, do the following:

python runserver

If everything is running correctly, you should see something like:

INFO:root:Checking for updates to the SDK.
INFO:root:The SDK is up to date.
INFO:root:Running application google-app-engine-django on port 8000: http://localhost:8000

However, if you are like me and saw an error like the following:

ImportError: No module named antlr3

Then you will need to install the antlr3 python module. Luckily this is easy.

  1. Go to and download the latest zip
  2. unzip
  3. cd antlr_python_runtime-3.1
  4. sudo python install

Lets see the site! When you go to http://localhost:8000/ you should see a page saying “It worked! Congratulations on your first Django-powered page.” Pretty (un)impressive huh?

Ok, now lets start doing something. Kill the server by pressing Ctrl-C. The Django tutorial is the next stop, which involves creating the Polls Django app. You can read through there to get a full understanding. For simplicity, I am only what I did to get it working.

python startapp polls
cd polls
from appengine_django.models import BaseModel
from google.appengine.ext import db

class Poll(BaseModel):
  question = db.StringProperty()
  pub_date = db.DateTimeProperty('date published')

class Choice(BaseModel):
  poll = db.ReferenceProperty(Poll)
  choice = db.StringProperty()
  votes = db.IntegerProperty()
  1. Edit (notice that order_by() from the Django tutorial is just order() here)
from django.template import Context, loader
from polls.models import Poll
from django.http import HttpResponse

def index(request):
  latest_poll_list = Poll.objects.all().order('-pub_date')[:5]
  t = loader.get_template('polls/index.html')
  c = Context({
    'latest_poll_list': latest_poll_list,
  return HttpResponse(t.render(c))
  1. cd ..
  2. Edit and add to urlpatterns (r'^polls/', 'polls.views.index'),
  3. mkdir -p templates/polls
  4. cd templates/polls
  5. Create index.html

  <p>No polls are available.</p>

  1. cd ../..
  2. Edit and add to INSTALLED_APPS ‘polls’,
  3. Now you can run the dev server again: python runserver
  4. And go to: http://localhost:8000/polls/
  5. You should see the message “No polls are available.”

Adding some data

You can go through the rest of the Django Tutorial to fill out the rest of the views. One last thing to know is the admin site. To view it, go to:


Notice that the Datastore Viewer is empty – it doesn’t even know about our Poll or Choice Models. Don’t panic. Go back to your terminal, and terminate the dev server. Now run:

python shell

This brings up a special python shell with the Django environment set up for you. Now you can run:

>>> from polls.models import Poll, Choice
>>> import datetime
>>> p = Poll(question="What's up?",

You have just created a new Poll. To end the shell, press Ctrl-D.

If you start the dev server again (or if you never stopped it in the first place), you should be able to go to:


to see you new Poll, and go to the admin site:


to see and create new Polls

Easy huh? :–)

Vegemite Beer Bread

I should have posted this on Australia Day (when we made it), but I haven’t got around to it until now.

Aussie Vegemite Beer Bread


  • 3 cups of self-rising (raising?) flour
  • 1 beer (375mL can or 12oz bottle)
  • 1 big knife-load of Vegemite
  • Grated Parmesan cheese
  • Left over butter


  1. Preheat the oven to 375°F (190°C)
  2. Lightly grease a small bread tin (about 9 x 5 x 3 inches) with the butter
  3. Get a big mixing bowl, tip in all the flour, add the beer and mix it up. We have found a whisk useless, but a spatula quite good
  4. If you like parmesan cheese as much as us, add as much grated parmesan to the mix as you wish
  5. Add the mix to the bread tin.
  6. Load up a knife with vegemite and run it through the mix – the vegemite will come of the knife and marble through the dough
  7. Bake for 60 minutes
  8. If you didn’t get your cheese fill, at the 40 minute mark, take the bread tin out, and sprinkle grated cheese on top of the bread
  9. After 60 minutes, you should be able to put a skewer into the bread and have it come out clean. Let the bread cool a little, cut and eat as fast as possible :–)

First Post – rant

Well, this is my first blog post, so what should I write about? Why not have a little rant about something I discovered recently (at least on Ubuntu).

sudo depends on DNS

WTF? Why does something like local privilege escalation, which does not leave the machine I am on, have anything to do with networking. Further, why the hell should a network configuration issue stop sudo from working. And even further still, why would Ubuntu (which as part of the normal install process does not set a root password) allow something as essential and necessary as sudo to be depended on a functioning network configuration? Amazingly though, a Google search showed this is a known issue. I really like the title of this bug: Manually Configuring Network Causes Massive, Unreversable, Failure. I believe this will be the first of many rants this blog will see, so readers (yes all 1 of you… thanks honey), check back soon. I’ll try and keep it G rated, but no guarantees :–)