"You listed HTML under programming languages, didn't you? Argh!"
IMHO, there's absolutely nothing wrong with listing HTML on one's resume, especially if one actually knows the context and how to use HTML to do something besides make text (for example, render) bold or italic.
Plain text resumes can indeed work to get information across, but if ever there were a way to demonstrate actual ability to code electronically, a resume coded in HTML would be that way. Resumes are about presentation. HTML, coupled with CSS, is a valuable way to demonstrate ability to present plain text.
Actually, thinking about it, most programming is essentially about presenting or rendering or parsing plain text, is it not? I would rather see somebody's hand-coded text/HTML resume than a plain-text text/text resume with (undemonstrative) HTML listed as a skill.
More on why job search is broken (and part of my startup philosophy):
There is a lot to be said for the meaning of irony when companies who claim to want creative and "out of the box" thinkers request that potential employees visit their website in order to submit the info on their resumes via little, pre-formatted text boxes.
What's wrong with using Blogspot? Surely the important point is the message, not the medium.
> IMHO, there's absolutely nothing wrong with listing HTML on one's resume
You managed to miss the point entirely: HTML is not a programming language.
I couldn't help thinking of this Calvin & Hobbes strip when I read that:
Actually, they're not. Resumes are communication, specifically a request with argument. Some of that argument is demonstrating good judgement, knowing that everything isn't a nail (even if you're a hammer swinger).
> HTML, coupled with CSS, is a valuable way to demonstrate ability to present plain text.
Valuable? It's not the least efficient way to present plain text, but the overhead didn't buy anything.
What happens when your resume is processed/displayed by something that knows nothing about html?
If I have to open a browser to read your "plain text"....
[indie@localhost~] $ firefox [indie@localhost~] $ gedit
I don't disagree with Mr. Yegge's assertion that plain text can be a decent way to present info on a resume if that is the only other option vs. discriminatory Microsoft .doc formatting, bullets, etc. . . . but his statement:
"HTML formatting usually makes it through safely because it's plain text. However, even if your tags are left alone by the automated mangler, there's no guarantee that your resume will be viewed from a browser, and nobody wants to read through a bunch of ugly markup while they're trying to assess your skills. So you shouldn't use HTML either."
Hello: programs (usually written by "programmers") are usually the entities doing this "automated mangling".
Anyway. I realize now that by putting "programming guru" in quotes, it seemed like I was attempting to insult the author's (SY's) skills, which I wasn't. . . apologies for that. I simply have an aversion to the word "programmer"; phrases like "programming language" seem really immature and pedantic to me. To me, code is the magic word.
What happens when your resume is processed/displayed by something that knows nothing about html?
If I have to open a browser to read your "plain text"....
If you are able to open a browser to read both plain text (source code) and a rendered page with some text, you can be pretty sure that the person who wrote the code knows what he or she is doing with both.
a. prepare paperwork that completely neutralizes my differentiating assets just to satisfy the automated processes of mindless drones
OR
b. start my own business.
DYHAQFM?
Nah, if you've got differentiating assets, list/show them! Yegge is just saying that people without any differentiating assets cover for that by filling their resumes with buzzwords and buzzphrases. Communicating your actual accomplishments clearly and succinctly should be sufficient.
At too many big companies, HR is used to screen, and all they know how to do is match buzzwords.
And that's just for starters (there's more to say on the topic of why job search is broken).
Employers need to realize the system is broken largely because of what they demand from candidates.
Think of this as a guide to help us make the process of scanning resumes just a little bit more manageable. :-)
I think that this post reveals how programmers are in the process of speciating - ie., diverging into seperate groups that are no longer capable of reproducing, resulting in different and incompatible branches of an evolutionary tree. Why? Because resume that Steve recommends will keep you from getting a job doing java for the accounts recievable department of a big corp, and the resume that will get you that big corp java job will prevent you from getting an interview with Steve.
Big corps are, first and foremost, looking for a pliable, good natured person who will follow directions and largely do as told. Within that context, they'd like as much talent as they can get, but they aren't willing to break the obedience requirement to get it.
Negative indicators for a big corp are: contributions to open source projects, an interesting an opinionated blog, microISV work, startup experience, substantial side work, passion for (or borderline obsession with) "obscure" programming languages (like LISP, ruby, smalltalk...) These things show that you might be trouble.
Positive indicators for bigcorp are: buzzword bingo resumes, weasel words, long lists of mainstream programming languages, databases and operating systems (like Java, C#, VB, MSSQL...), vendor certification in the above list. These things suggest to the big corp that you'll play their game the way they like it played.
It turns out that you can't really cover both bases, which is why I call this speciation. We're rapidly moving toward a point where these two groups will no longer be able to interact or cross-pollinate. You can't be a bigcorp programmer and an innovative hacker at the same time, any more than you can be a sea cucumber and a clownfish the same time. One excludes the other.
Fortunately, you get to choose - and you can change.
""Lead" is ... the present-tense verb meaning "not doing any coding""
At least, that's what it was like a year ago.
A lot of places just say "email a resume" and don't specify whether they mean send an "email resume" or an "email with a word doc attached" or an "email with a text resume attached" or "html-email" or "email with html attachment" or "pdf." You just have to guess. I typically would send a rich text, informal email cover letter with a few lines, then I'd attach the resume as html and word doc.
