This book was awesome. I give it 5 of 5.





Two years ago I stumbled upon a little essay entitled “How to Become a Hacker“. I was enthralled.
I’ll be honest and say that I read that essay hoping to learn how to become a cracker. I had booted my company laptop, let it go to sleep, and then closed the lid and forgot about it for a few months, and when I came back could not remember the password. It would not let me reinstall windows, it would not let me install linux, I could not format the hard drive, it was LOCKED.
I got pissed. Here I was, a “geek”, and I couldn’t get around a stupid M$ password??? Couldn’t all the awesome computer people on tv and movies slice through passwords like warm butter? Where could I learn to control my computer instead of letting my computer control me? I was sick and tired of being told what I could and couldn’t do, and how I could do it by my computer. I should be ordering it around. I should be the master of my machine.
So I went to Google and entered the words that would change my life: “How to be a hacker”.
I clicked on the first thing that came up on the screen, and spent the next few hours reading and re-reading the essay. I had found what I wanted to do. I wanted to be a hacker. Not a cracker, (I didn’t even care about the stupid laptop anymore, and in fact, I think it got tossed after no one could crack it) no, I wanted to be a hacker.
So away I went to learn. Almost immediately I talked with one of my teachers (Andy Harris) about what I had read. His response was something along the lines of “Some random guy on the internet can’t tell you how to be a hacker, or even what a hacker is. You have to find that for yourself.” or something like that. I think what he meant was, “You can’t just learn a few languages, and then expect to be called a hacker” (which wasn’t what the essay was saying, but I must have explained it really poorly. I think his main beef was with the hacker emblem for some reason). But still, I liked the whole concept, and so I signed up for the CS certificate (it was too late to switch to the bachelors).
I had a lot going on in my life, and almost completely forgot about the essay in my obsessive grind to hackerdom. To start I honed my HTML skills, and soon got a job as a PHP programmer for IUPUI. Then I got a job programming Java. Time went by and I forgot more and more about the essay.
Then, one day I picked up “The Cathedral and the Bazaar” in Half Price Books. I had just finished “Dreaming in Code” (which I just now realized I forgot to review. It’s worth the read, but fizzles towards the end) and I recognized the title (of The Cathedra and the Bazaar) from references Scott Rosenberg (Dreaming in Code) had made to it throughout the book. It looked interesting so I thought I’d check it out.
It was awesome. It reminded me of something I had read what seemed like ‘a long time ago, in a galaxy far far away’ before I became serious about being a “Computer Scientist” (as I had come to call it). Then I came to the end of the book, and saw that ‘Appendix A’ was entitled “How to Become a Hacker”. Wait a minute… I’ve read that before…
So I read it again. This time with the knowledge that it wasn’t written by “some random guy on the internet” as my teacher had put it, but by someone almost as well known (in the hacker community) as Linus Torvalds. Sweet.
It was almost exactly two years ago that I read the essay for the first time, although it seems like at least five years have gone by.
On the coding requirement part of it, I now know two languages decently well (PHP and Java), which leaves me with Python (I was ‘supposed’ to learn that first, but didn’t, should be a breeze at this point), C/C++, and Lisp (I get the impression that PHP has replaced Perl). I’m thrilled at the prospect at learning these languages over the next few years.
I am also psyched about joining/starting an OS project now that I have something substantial to contribute. I’m either going to make an OS Python version of my (incomplete) Flash TD game, or I’m going to join the Chandler project. Knowing me, I’ll do both.
Now, back to the book.
It answers tons of questions about Open Source that I have had (Like: ‘How do you make money if you give everything away?’). It is a great read, and actually fun at some parts (like when the author tells about the time he led a march on Microsoft dressed as Obi-won with a giant penguin behind him that shouted the words “Let the source be with you!”). It describes the differences between developing closed source projects (the cathedral) and open source projects (the bazaar) and why closed source takes way longer, and has fewer features most of the time. You can read most of the book on the author’s website since it is just a bunch of continually updated essays.
The more I learn about hackers and OS, the more I see parallels between Lord of the Rings and the history of computers. Microsoft reminds me a lot of Morgath, who wanted to bend and hoard all of creation to himself rather than create and share creation cooperatively like the other Valar.
For clarification, in case I didn’t make it clear, a hacker is not a criminal. Hackers make things, crackers break them. When the media refers to “hackers hacking into government databases” or stuff like that, what they mean is “crackers cracking into government databases”. Crackers love to call themselves hackers, but they are not. The term hacker was invented back in the 1970s (I think) by computer experts who wanted to give themselves a label, and then misappropriated by the media in the late 80s early 90s…