Resumés are funny things because the one thing they don’t tell you is the one thing you want to know. As an employer, what I suspect I really want is a way to separate wheat from chaff. I want a way to say “Yes, fine, you have all the necessary checkboxes in place, but are you one of the good ones?” Even if you allow yourself the confidence necessary to believe that you are indeed one of the good ones, a resume is a terrible medium since, stylistically, it tends to force people down the path of enumeration-sans-substance. What is needed is a shibboleth. Don’t tell me which certifications you have, tell me that you are part of the culture. Don’t tell me what programming languages you know, tell me that you can kick ass and take names. Everyone who isn’t a bozo (seriously, go read that if you’re ever hiring someone) should be trying to hire the brightest lights in the building, so show them how you roll, or find another job to apply for.
That is how I would like things to go down, but even very hip HR folk would have trouble with a shibboleth resumé, I’m guessing. If I were applying for a job tomorrow, it would probably be something involving usability, security, and overall technology development. The resumé I’d send to a shibboleth-friendly company might read like this (standard disclaimers about the fact that any decent resumé almost automatically sounds boastful and egocentric; my apologies): Continue reading “Shibboleth Resumé”
I don’t think it’s very normal of me, at the tender young age of 28, to enjoy the
An article of faith among Canadians is that not only do we know more about our country than Americans know about theirs, but we know more about the US than Americans do, as well. This may or may not be true on balance, but I will let sleeping sacred cows lie. For those who wish to get their self-congratulatory freak on though, behold:
Software development, like most of engineering, and maybe like most of organized human production, has two sort of obvious approaches to solving a given problem. One is to start from the top and work down. Maybe the top is the higher level of abstraction. Maybe the top is the user interface. In some sense, the “top” is seen as the generic, “high-level”, gestalt view of the world. The style of development that begins from this point is known quite universally and unsurprisingly as “top-down”.
[This really isn’t an article for one person, but there’s one person out there who will think it is about her, and in a way it is – if she weren’t talking about this then maybe I wouldn’t be thinking about it and writing about it just this very second. Nothing in here is specific to her situation though, and with money it’s almost always about the specifics of your situation, so grains of salt all round.]
The IBM Toronto Lab is a bit of a misnomer. Shortly after I joined we moved out of Toronto, up to Markham, to a brand new lab on a relatively large chunk of property (our ribbon cutting ceremony was September 11, 2001). The nice thing is that this relatively large property is also basically undeveloped except where the buildings and parking lots stand, leaving a fair bit of genuine certified nature lying about. I’ve been keeping a bit of a list, and so far in 2006 I’ve seen (in addition to plants and insects):