Hacking Work – or how to write a book about nothing at all

"Hacking Work" CoverI recently travelled on an aeroplane to the Boxing Day cricket match in Melbourne. Before the flight home I was killing some time in the Borders in the terminal, when a book caught my eye. It’s name? Hacking Work, by Bill Jensen and Josh Klein.

After reading the back cover, I bought the book immediately. Who wouldn’t want to work smarter and get more done with less effort? It’s me in a nutshell. Unfortunately, I was very disappointed.

For most non-fiction books, the back cover is a very rough summation of the goal of the book, along with a few of the more interesting little titbits. For this book however, the blurb is the entire contents of the book. The other 200 odd pages are just fluff.

Section 1 of the book tells the reader that they are special, are born to “hack” work, and that managers will get in the way of everything.

Section 2 of the book tells the reader that they are special, are born to “hack” work, and that managers will get in the way of everything.

Section 3 of the book tells the reader that they are special, are born to “hack” work, and that managers will get in the way of everything.

Section 4 of the book tells the reader that they are special, are born to “hack” work, and that their employees will try to hack work too.

Unfortunately, nowhere in this book are there actual instructions for any methods of actually getting more done in less time. There are occasional snippets detailing what people have done before, usually followed by “we don’t recommend actually doing this”.

I personally consider myself somewhat of a life hacker, and this is a travesty of a book about “hacking”. The severe degradation of the meaning of the word “hack” is beyond annoying, it’s almost insulting.

Zero stars. I wouldn’t read it if it was free.

30 Days of Geek #13: How did you become such a geek? Career? Personal interest?

I’ve decided to partake in Jethro Carr’s 30 Days of Geek challenge, so I’ll be writing a post a day on my geekiness for an entire month! You can find all the posts in one spot here. Apologies for the lateness of today’s post, I was busy yesterday.

It was such a long time ago that I became a geek that I’ve sort of forgotten how it came to be.

Back when I was around 14 or so my stepfather bought me and my brother a computer, to stop us using his office computer to play games. As well as playing countless hours of Age of Empires and Grand Theft Auto, I spent quite a lot of time ‘making my computer better’, which really involved breaking it and having to reinstall Windows every few months.

Even before that though, I was messing around with a BASIC interpreter (QBASIC on MS-DOS) on the office computer… it must have been back in 1998-1999. I thought “Hello, world!” was a masterpiece. For a 9 or 10-year old, I guess it was. At that stage, anyway. I’ve met 13-year olds writing operating systems now. Kids these days.

It’s definitely personal interest, but I hope to make it into a career.

30 Days of Geek #3: What does your day job involve?

I’ve decided to partake in Jethro Carr’s 30 Days of Geek challenge, so I’ll be writing a post a day on my geekiness for an entire month! You can find all the posts in one spot here.

I’ll answer this question in two different ways.

My “job” is working as a computer technician for a computer shop based in Hobart, Tasmania. I only work on Saturdays (at the moment, it used to be full-time), so that leaves me quite a bit of the week free for other pursuits. My work involves three main parts:

  • Fixing dead computer hardware. 90% of the time it’s a dead power supply, which is an easy fix, but occasionally there are some amazing problems that just shouldn’t happen. And those are a good fun learning experience.
  • Fixing broken Windows installations. 90% of the time it’s a virus, which is an easy fix, but occasionally there are some amazing problems that just shouldn’t happen. And those are a bastard. Most non-Microsoft application developers are stupid and lazy, it seems.
  • Dealing with customers on the phone. This is both the best and worst part of my job.

I’m fairly lucky with my work, in that I get paid to learn. 🙂

The activity that I spend most of my week doing is system administration. I don’t get paid much for this (not yet, anyway), but I’m continually learning and one day I’m going to have 1337-h4x0r skills (no, really). I have the feeling that system administration is where I will probably end up in my career.

Back at University

Today, seeing that I haven’t done so for a while now, comes an update on my life.

I’ve just started my second year at university. My degree is supposed to be three years long, but I’ll stretch it out to three and a half because I failed stuff bigger is better. I’m still doing computing. This year comes one of the units I’ve eagerly anticipated: Algorithms. It’s programming in C, finally, after a year of Java. Also comes a not-so anticipated unit, ICT Project Management. It’s as dull as it sounds.

I’m not really sure why I’m at university. Mostly just because I can’t figure out anything else worth doing. I could go get a job, but having done that before, university seems much easier. I enjoy playing around with computers and programming, but I’m not quite confident that I really want a job as a programmer… I should probably figure that out soonish.

After resigning from Principal Computers again before I left to move to Berlin in July last year (which I ended up not doing, sadly enough), I’m now back there working Saturdays again. And I still jump every time the phone rings. Talk about Pavlov’s dog.

I’ve started playing around with Cisco networking gear again. This time I’ve got a 3550 switch, which strangely enough is more of a 24-port router than a switch. It can do some weird and wonderful things. I can’t wait to do the networking unit at university.