jump to navigation

The Origin of “Hacker” April 1, 2008

Posted by Imran Ghory in Computer Security, etymology.
30 comments

Everytime the media carries a sensationalist story about “hackers” committing cybercrimes there’s always an uproar among geeks about the misappropriation of the word “hacker”. Sadly it’s the geeks who are mistaken and not for once the media.

A few years ago Fred Shapiro tracked down the earliest known reference to computer hackers:

1963 The Tech (MIT student newspaper) 20 Nov. 1 Many telephone services have been curtailed because of so-called hackers, according to Prof. Carlton Tucker, administrator of the Institute phone system. … The hackers have accomplished such things as tying up all the tie-lines between Harvard and MIT, or making long-distance calls by charging them to a local radar installation. One method involved connecting the PDP-1 computer to the phone system to search the lines until a dial tone, indicating an outside line, was found. … Because of the “hacking,” the majority of the MIT phones are “trapped.”

This is the earliest know usage of hacker in the modern sense, the TMRC Dictionary has it a few years earlier but not in the computer sense. The earliest computer related uses of the term (through anecdotal evidence) were also malicious (although the term wasn’t originally intended maliciously – in practice it was) in the sense that they involved gaining unauthorized access to computers to play on.

The New Hacker's DictionaryThe modern “geek” definition of the term hacker to reflect a skilled programmer didn’t originate until the late seventies when the term ended up in the later famous Jargon File.

Intelligent Design for IdiotsThat doesn’t mean to say we should all stop using the word “hacker” in it’s positive sense, but as evidence advocating geeks we should at least stop claiming a false history to support our cause. As we all know where that ends up.

In response to those who disagree with me: If you think I’m wrong then show me the evidence, if you can find earlier records showing hack(er)s being used in a computer context in a non-“black hat” manner I’d be happy to retract my post and put the evidence up here.

Advertisements

Studying for Job Interviews isn’t cheating April 1, 2008

Posted by Imran Ghory in job interviews.
9 comments

Teacher: Does anyone know why breaking mirrors is bad luck ?
Boy 1: [long boring in-depth explanation]
Teacher: Well done that’s exactly right have some merit points
Boy 2: That’s not fair, he’s cheating, he’s been reading up on it.
Teacher: That’s not cheating, that’s the point of school

Some of the respondants to my earlier posts on interviewing seem to be of the opinion that studying books which teach you to do interviews is a form of “cheating”, that reaction caused me to remember the above scene from my childhood.

Interviews are just like any other test, studying up is expected and necessary. Sure if you’re good you can just breeze into a test without preparation and get an ok mark. But interviewers mark to a curve.

If you’re not on the top you’re not going to get in with an “ok” mark. A quick look at Amazon reveals a staggering 1152 books on interviewing – improving interview skills obviously isn’t a small market.

It’s arguable that interviewers should take into account how good the person genuinely is and not how well they perform in an interview. That’s actually very hard. You can tell if a candidate is reciting an earlier memorized answer, but a lot of the time you can’t tell if the candidate has just practiced a lot of interview questions.

The other solution to equalizing the impact of studying beforehand is to tell everyone to study up and let that balance everyone out, and that in part is what I’m trying to do here.

When I was a student and looking for my first job I interviewed with a number of software development companies, in most of the interviews 70-80% of the questions asked were straight out of one of the interview books I had read. I can only imagine how the other candidates who went into the interviews unprepared coped.

Of course improvement doesn’t occur in a void, if a candidate practices it won’t just improve their interview skills it will also improve their underlying skills which is what the interviewer is trying to measure.

Most companies wouldn’t hesitate to reject an interview candidate who hadn’t read up on the company beforehand. Shouldn’t that extend to interviewing skills in general ?

After all learning to interview well shows motivation, self-study skills and preparation. Three things which are notoriously hard to measure in interviews. Even if I could easily identify candidates who’ve practiced for the interview, I’m not sure I wouldn’t consider it a plus rather than a negative.

A bad candidate with good interview skills isn’t going to seem like a good candidate in interview (at least in technical interviews where “all-talk” candidates typically fall down, regardless of how much they’ve tried to memorize). It might however make an average candidate seem good – but then I think I might prefer an average candidate who’s motivated, self-studying and well-prepared over a good candidate who survives on pure talent alone. It would certainly be a close call.

So if you’ve got an interview coming up, then take a moment to go down your local bookstore or browse through Amazon and pick up a book to brush up your interview skills.

Because if you don’t you may lose the job to someone who did.