• mabinogi (unregistered) in reply to kimbo305
    kimbo305:
    some dude:
    Uh, oh. I think we found Alvin. Either that or someone *seriously* forgot their <sarcasm> tags.
    They just weren't good at sarcasm.

    That's because it wasn't sarcasm, it was irony. And telling people something was irony completely destroys it. Part of the point is that some people will take you literally, but those that think the same way as you will understand that it's a joke.

  • CastrTroy (unregistered) in reply to Hej
    Hej:
    I hope the "C-pound" was a joke, though I didn't get the sense of 'ha ha' afterwards....
    I heard a story about a guy who worked on ASP web pages that called it asp, like the snake, instead of A-S-P. It's not completely unbelievable. According to a the "Mastering Regular Expressions" book I just finished reading, Regex is pronounced with a hard "G", like gone. However, having only seen the word on the internet and books, and with my knowledge of how English usually works, I've always pronounced it with a soft G, like in giant. C-Pound is a little hard to believe, but I could see it happening.
  • incoherent (unregistered) in reply to Chris
    Chris:
    Top Cod3r:
    Its obvious that Brent, having lacked experience in hiring developers, failed to accurately advertise the requirements for the position he was trying to fill. Now that he has gotten the wrong type of candidate, he's trying to cover up his own mistake by ripping on the applicant.

    If it were me, I would hire Alvin immediately after the phone interview, because its obvious that he is the kind of go to guy who you can count on to find the answer and solve problems on his own using Internet resources when necessary. And they didn't say, but if this was a telecommuniting position, he seems like the perfect fit.

    Maybe Brent should go read some books on interviewing skills and not publicly ridicule applicants for his job posting. Its no wonder he can't hire anyone.

    Surely you can't say that you would hire this guy? I man if you are recruiting for an experienced coder and the guy is simply regurgitating what he sees on a website you can't honestly expect him to have the understanding required for the role? I dont think the guys interviewing skills are at question here, if the interviewee clearly has no clue about the questions asked then it's not the interviewers fault.

    I think the interviewee was just trying to be optimistic in his skills and hoping to get lucky with a job. Whilst he has shown some google skills I don't think you should be hiring everyone who can put "static class" into google.

    Every day Top Cod3r posts something ridiculous, and every day someone bites on it. Continue feeding the trolls, people...

  • Dave (unregistered)

    When I'm hiring someone and I have a bunch of applicants, I want as much information as possible to identify who qualifies for an interview. Who are you people that can say yes or no to someone based on 1.5 pages? I really don't want to waste my time interviewing someone who has provided a page of TLA's, I want a story so I can start to build a picture of the person. Obviously if the story isn't well written or gets boring after the first page I can stop reading but as with most things, I find the more I know, the better able I am to make a decision and the more confidence I have in the choices I make. In NZ once a person is hired for a position it is very difficult to then sack that person for non-performance so you need to be very sure you're hiring the right individual.

    Having said that we had a developer we hired recently show up for the first week and then just vanish (http://www.computerworld.com/blogs/node/5530).

  • kr00ls (unregistered) in reply to Dave Krause

    Agree. What I noticed is that for consulting gigs people tend to submit longer resumes, which list the technologies and short descriptions of the projects. I would say that average resume of a consultant that my company receives is 10 pages, although I have seen 20+ pages... Its fairly common especially if one is a consultant with multiple masters or a phd. I have to admit it is very very depressing when I compare it to my mere 2 pages ;) But when you look at it from a different perspective, you might question one's knowledge of the technologies they listed. Many times, people with 5+ page resumes do not remember what they coded 2 years ago... or when questioned in detail, will admit "err err I have worked it with BUT..".. and it turns out someone else did the work, while they just looked at it :).

  • Nick (unregistered) in reply to Martini
    Martini:
    Diamonds:
    I would have asked what keyword do you use to create a 'goatse' class.

    That would have given him the clue to not lookup the answers to questions.

    PS: Don't google that word.

    Don't google "pain series" either. Really NSFW. Or viewing in general.

    If ever it was appropriate...My eyes! The goggles, they do nothing!

  • tyrannical (unregistered)

    The C# C pound / C sharp isn't that much of a WTF.

    I remember my database classes in college, SQL was pronounced with the letters S-Q-L. I had never heard it pronounced as "sequel" I still don't know why you would pronounce it as sequel either.

  • (cs)

    If you call SQL "sequel", why can't you call ASP "asp"?

    Sure, it MAY be the fact that the person calls it so because he knows nothing about the language, but the latter is non sequitur from the former alone. Asp is faster to say than A-S-P, so I see no reason not to use this pronunciation.

    P.S. Personally I like calling SQL "squirrel" (especially MySQL -> My Squirrel. Why? Because it's very small, very agile, and you never know when you are going to step into some of its shit)

  • Woo (unregistered) in reply to tyrannical

    Well, SQL was originally called SEQUEL before the name had to changed due to some trademark problems so it's pretty reasonable to find people (espeically people who were in the industry back when SQL was pretty new) who still call it that.

    I go back and forth on it myself.

  • smart (unregistered)

    Overloading, maybe, is when a developer is given more jobs than its normal.

  • k (unregistered) in reply to Bomm

    You know it never occurred to me before now that the time it takes to read longer CVs would be an issue - but I suppose it could well be.

    It hasn't occurred to me because I have (about) an 1100 wpm reading speed (always have had, just like that). I used to read (and mostly reject) hundreds of CVs a day as well as my regular development work, and never thought anything of it.

    My CV hovers around 4-5 pages, never had any issues, agents always seem to think it's very good. Just listing the places you have worked and your position takes space given most of us change jobs every couple of years...

  • Iceman (unregistered) in reply to SamP
    SamP:
    If you call SQL "sequel", why can't you call ASP "asp"?

    Sure, it MAY be the fact that the person calls it so because he knows nothing about the language, but the latter is non sequitur from the former alone. Asp is faster to say than A-S-P, so I see no reason not to use this pronunciation.

    P.S. Personally I like calling SQL "squirrel" (especially MySQL -> My Squirrel. Why? Because it's very small, very agile, and you never know when you are going to step into some of its shit)

    I've heard it pronounced "squeal" on several occasions :-)

  • Grammar Police (unregistered) in reply to diaphanein
    diaphanein:
    I definitely look down upon 6 pages of resume. Especially when its riddles with typos and bad grammar. Not that I'm trying to be grammar/spelling police, by any means, but people, please. Your resume is the first (and potentially last) impression you make with an interviewer. PROOF READ.

    If you're going to play the role of grammar Police, despite the addendum of not actually doing that, which, in my book, is worse, at least get your own house in order.

    I recently had a guy that graduated in "Sprint 2005". (Although, spelling and grammar aside, he actually turned out to be a good interview).

    He made the mistake you're telling people not to make, yet you interviewed him anyway? Curious.

  • 3Peso (unregistered)

    Man, this was the best laugher of the month! Hadn't so much fun in the last several months ^^

    Uhm, ok, time to get back to my 'unmanaged' code ^^

  • (cs) in reply to CastrTroy

    Would have sounded better in Dobly.

  • Nico (unregistered) in reply to CastrTroy

    It makes sense when you consider that regex is short for "regular expression".

  • I Like Pie (unregistered) in reply to Nico

    Acronyms are routinely pronounced as a word. Anyone who looks down on this is clearly far too up themselves.

    No one says L.A.S.E.R do they?

    Captcha: Onomatopoeia.....thats just far too non-random.

  • Dave (unregistered) in reply to SM
    SM:
    Jonh Robo:
    ...my resume is 6 pages long to cover all of my IT experience spanning nearly 30 years. I figure if the hiring manager really wants to know me they have the info. Sure, they can stop reading as soon as they have the info they need. They don't have to read all of it.

    I know this is not the "accepted practice" for resume length...but I'm exceptional!

    OK, but when it's that long there's a good chance that they probably just won't read any of it.

    There seems to be different schools of thought on this. I was always told to limit it to 2 pages but, having sifted through a fair few CVs myself, prefer to read through a properly spaced, clearly laid out CV in a decent sized font - it's there to help sell yourself to prospective employees, not to be quick for them to print-out.

    Making it hard to read and hard to digest just to cut it down to 2 pages is counter-productive.

    My CV currently weighs in at 5 pages consisting of a cover page for HR, a tech. skills page for reference / clarity, 2 pages covering past experience and interests, etc. My contact details and references stand alone on the 5th page as recruitment companies omit these when forwarding CVs.

    It's also worth seeing what extra formatting recruitment companies apply to your CV as this can often make a poorly laid out CV even harder to read.

  • TheRealFoo (unregistered) in reply to diaphanein
    diaphanein:
    Not that I'm trying to be grammar/spelling police, by any means, but people, please.

    If people can't spell correctly in their own resume, they can't spell when programming, either.

  • anon (unregistered) in reply to Top Cod3r
    Top Cod3r:
    Its obvious that Brent, having lacked experience in hiring developers, failed to accurately advertise the requirements for the position he was trying to fill. Now that he has gotten the wrong type of candidate, he's trying to cover up his own mistake by ripping on the applicant.

    If it were me, I would hire Alvin immediately after the phone interview, because its obvious that he is the kind of go to guy who you can count on to find the answer and solve problems on his own using Internet resources when necessary. And they didn't say, but if this was a telecommuniting position, he seems like the perfect fit.

    Maybe Brent should go read some books on interviewing skills and not publicly ridicule applicants for his job posting. Its no wonder he can't hire anyone.

    There can be no doubt- "Top Cod3r" is Alvin. Hey Alvin, now that you know what static means, can you tell us what instantiate means? How's that "solving problems on [your] own using Internet resources", learning how to code one frigging word at a time thing working out for you?

  • Arno Hayes (unregistered)

    My worst CV blooper ever was when I misspelled MENSA on my last one. Luckily I got the job anyway, but I'm still embarrassed about that one :P

  • ze REEEL german! (unregistered) in reply to CastrTroy
    CastrTroy:
    Hej:
    I hope the "C-pound" was a joke, though I didn't get the sense of 'ha ha' afterwards....
    I heard a story about a guy who worked on ASP web pages that called it asp, like the snake, instead of A-S-P. It's not completely unbelievable. According to a the "Mastering Regular Expressions" book I just finished reading, Regex is pronounced with a hard "G", like gone. However, having only seen the word on the internet and books, and with my knowledge of how English usually works, I've always pronounced it with a soft G, like in giant. C-Pound is a little hard to believe, but I could see it happening.

    Well, if you know that "Regex" ist just a short for "Regular Expression", it makes sense NOT to pronounce it with a "soft G" like in "giant".

    You wouldn't pronouce "Regular" that way, would you?

  • (cs)

    Static class - students sit still in the class Non-Static class - students jump around, making noises in the class.

  • grammar jerk (unregistered) in reply to diaphanein
    diaphanein:
    I definitely look down upon 6 pages of resume. Especially when its riddles with typos and bad grammar. Not that I'm trying to be grammar/spelling police, by any means, but people, please. Your resume is the first (and potentially last) impression you make with an interviewer. PROOF READ. I recently had a guy that graduated in "Sprint 2005". (Although, spelling and grammar aside, he actually turned out to be a good interview).

    I love posts about grammar that have bad grammar themselves. Proofread is one word. Riddles is the wrong tense. "but people, please" is a goofy colloquialism. Yay!

  • Hognoxious (unregistered) in reply to TheRealFoo
    TheRealFoo:
    If people can't spell correctly in their own resume, they can't spell when programming, either.
    Not an issue, just don't use 'option explicit' or the like.

    [ducks for cover]

  • (cs) in reply to Tatiano
    Tatiano:
    my resume is 73 pages long...

    i like to include nice full-page pictures of photos over a wooden table showing me and the things i like and dislike...

    Don't forget to include your level 43 Dwarven Fighter.

  • A Zanescu (unregistered) in reply to RogerN

    In C# 2.0 it can and it constrains that class to contain only static members

  • NeoMojo (unregistered) in reply to anon
    anon:
    Top Cod3r:
    Its obvious that Brent, having lacked experience in hiring developers, failed to accurately advertise the requirements for the position he was trying to fill. Now that he has gotten the wrong type of candidate, he's trying to cover up his own mistake by ripping on the applicant.

    If it were me, I would hire Alvin immediately after the phone interview, because its obvious that he is the kind of go to guy who you can count on to find the answer and solve problems on his own using Internet resources when necessary. And they didn't say, but if this was a telecommuniting position, he seems like the perfect fit.

    Maybe Brent should go read some books on interviewing skills and not publicly ridicule applicants for his job posting. Its no wonder he can't hire anyone.

    There can be no doubt- "Top Cod3r" is Alvin. Hey Alvin, now that you know what static means, can you tell us what instantiate means? How's that "solving problems on [your] own using Internet resources", learning how to code one frigging word at a time thing working out for you?

    You might already be aware but, top cod3r is a troll and often makes an appearance in a thread, posts something stupid and then leaves. if you see top cod3r in future, just ignore it.

  • kr00lis (unregistered)

    In my freshman year, I have taken Engineering Orientation class, which dealt with introduction to the College of Engineering, policies, procedures, resume writing, etc. We had a speaker from a career center who said that one time someone submitted a resume with an objective: "Seeking a position (...) which will (...) in the pubic area". They missed it and submitted it for consideration and found out about when one vendor called and complained :P Out of curiosity; how many people have the objective in their resumes?

  • Matt (unregistered) in reply to whicker
    whicker:
    I never understand these fake facades people create in an interview setting.

    If a person is that bad, why even thank the person for the time spent and why even give the "will contact you in a few weeks" speech?

    If you want employees to be honest in their interviews, why do the people hiring feel they need to hide their true impressions?

    Let that person know it. What's the worst that person can do, actually gain the knowledge required for that position? Or, are hiring people afraid that as candidate F's number of interviews with constructive feedback increases without bound, the probability of passing the screening without actually having the skills approaches 1?

    Because in this country everything you say can and will be held against you in a lawsuit.

  • anon (unregistered) in reply to Arno Hayes
    Arno Hayes:
    My worst CV blooper ever was when I misspelled MENSA on my last one. Luckily I got the job anyway, but I'm still embarrassed about that one :P

    You should be embarrassed to put MENSA on your CV in the first place. Have you really lived such a pitiful life that you need to say, "please disregard my lack of accomplishment, for I have a high IQ"?

  • (cs) in reply to CastrTroy
    CastrTroy:
    Hej:
    I hope the "C-pound" was a joke, though I didn't get the sense of 'ha ha' afterwards....
    I heard a story about a guy who worked on ASP web pages that called it asp, like the snake, instead of A-S-P. It's not completely unbelievable. According to a the "Mastering Regular Expressions" book I just finished reading, Regex is pronounced with a hard "G", like gone.

    "Regex" is no more pronounced with a hard "g" than does it have an unstressed vowel in the "ex". That book is clearly full of crap. Acronyms are not necessarily pronounced as the sum of their parts.

  • (cs) in reply to diaphanein
    diaphanein:
    I definitely look down upon 6 pages of resume. Especially when its riddles with typos and bad grammar. Not that I'm trying to be grammar/spelling police, by any means, but people, please. Your resume is the first (and potentially last) impression you make with an interviewer. PROOF READ. I recently had a guy that graduated in "Sprint 2005". (Although, spelling and grammar aside, he actually turned out to be a good interview).

    Did you mean "it's riddled with typos and bad grammar." instead? PROOF READ. Always a good suggestion; just wish more people would pay attention.

  • (cs) in reply to whicker
    whicker:
    I never understand these fake facades people create in an interview setting.

    If a person is that bad, why even thank the person for the time spent and why even give the "will contact you in a few weeks" speech?

    If you want employees to be honest in their interviews, why do the people hiring feel they need to hide their true impressions?

    Let that person know it. What's the worst that person can do, actually gain the knowledge required for that position? Or, are hiring people afraid that as candidate F's number of interviews with constructive feedback increases without bound, the probability of passing the screening without actually having the skills approaches 1?

    Maybe because stopping mid-interview and saying to the interviewee, "Sorry, but you're dumb as a box of rocks and don't know a damned thing about programming. We're not interested." is considered to be bad manners, and looks bad for the company the interviewer is representing?

    I worked for a Fortune 100 company. Our hiring process was to have our internal recruiters collect resumes. An actual developer would review the resumes and decide which ones might be worth looking into further. Recruiting would then call those candidates and schedule a 30-minute technical interview by phone with one of our developers. People who did well on the phone interview were then brought in for three half-hour interviews, back to back, with two other developers and a manager, and then a half-hour meeting with the recruiter for HR-related stuff.

    I did a lot of the tech phone interviews, and was amazed at the ways that people tried to BS their way through. Like the guy who, after every single question, would do a "cough. cough. [sound of keyboard] cough. cough. Well..." before answering. Google anyone? Or the guy who said "Ummm... Let me think for a second." and as he said it you could hear the pages of the book he was trying to find the answer in turning in the background.

    Still, even with those people, I asked all of the questions I'd prepared, and a couple of follow-ups when they managed to come up with a somewhat accurate answer, because I was representing the company I worked for; if I'd been representing just myself looking for a short-term assist, I'd still have done the same.

  • (cs) in reply to TheRealFoo
    TheRealFoo:
    diaphanein:
    Not that I'm trying to be grammar/spelling police, by any means, but people, please.

    If people can't spell correctly in their own resume, they can't spell when programming, either.

    There's that, and attending to details ...

  • (cs)

    The fact that "Alvin" didn't seem to comprehend basic programming concepts aside, I see no problem with looking things up like that. Any competent interviewer would understand that asking a "memorization" question is stupid when it comes to programming since one can easily find the answer. If anything, looking it up shows resourcefulness on behalf of the interviewee.

    I've admitted in the past that I'm not sure of the immediate answer to a question during a technical interview, followed by mentioning what I do know/remember relating to it, and the comment that I could easily use Google/MSDN/etc. or purchase a book and freshen up on the subject. If the interviewer holds that against me, then they're probably not something I wish to work with anyways.

  • CmdrFire (unregistered) in reply to Martini
    Martini:
    Diamonds:
    I would have asked what keyword do you use to create a 'goatse' class.

    That would have given him the clue to not lookup the answers to questions.

    PS: Don't google that word.

    Don't google "pain series" either. Really NSFW. Or viewing in general.

    Argh! My eyes!

  • dsh (unregistered) in reply to versatilia
    versatilia:
    a list of technologies worked with (mostly TLAs - I even added "TLAs" as a joke),

    TLA isn't a joke, it's "Tom Lord's Arch" (http://www.gnuarch.org/)

    :)

  • anon (unregistered) in reply to TheRealFoo
    TheRealFoo:
    diaphanein:
    Not that I'm trying to be grammar/spelling police, by any means, but people, please.

    If people can't spell correctly in their own resume, they can't spell when programming, either.

    So? In coding, spelling consistently matters, not spelling correctly.

  • (cs) in reply to Grammar Police
    Grammar Police:
    diaphanein:
    I definitely look down upon 6 pages of resume. Especially when its riddles with typos and bad grammar. Not that I'm trying to be grammar/spelling police, by any means, but people, please. Your resume is the first (and potentially last) impression you make with an interviewer. PROOF READ.

    If you're going to play the role of grammar Police, despite the addendum of not actually doing that, which, in my book, is worse, at least get your own house in order.

    There's a big difference between a typical grammar nazi post and that. That post is giving resume advice (albeit advice that should be painfully obvious and is said a lot), while most are just correcting people.

    And it's a post on an internet forum... it shouldn't be held to the same standards a resume is.

    Nico:
    It makes sense when you consider that regex is short for "regular expression".
    ze REEEL german!:
    Well, if you know that "Regex" ist just a short for "Regular Expression", it makes sense NOT to pronounce it with a "soft G" like in "giant".

    You wouldn't pronouce "Regular" that way, would you?

    Yeah, but enough things DON'T make sense that it's far from a foregone conclusion. "char" is short for "character" so, by that logic, should be pronounced almost like "care", but in my experience, both "car" and "char" (like charred wood) are more common.

  • Frank Stimpleton (unregistered) in reply to diaphanein

    I once read a resume that told me the applicant had done major "implantations" of code into production.

    Into the "B pile" right away.

    CAPTCHA: darwin (no kidding?)

  • (cs) in reply to ze REEEL german!
    ze REEEL german!:
    Well, if you know that "Regex" ist just a short for "Regular Expression", it makes sense NOT to pronounce it with a "soft G" like in "giant".

    You wouldn't pronouce "Regular" that way, would you?

    More to the point, you should never be trying to pronounce an abbreviation to begin with. Just say regular expression. Abbreviations are to save you time writing, not speaking.

  • (cs) in reply to anon
    anon:
    TheRealFoo:
    diaphanein:
    Not that I'm trying to be grammar/spelling police, by any means, but people, please.

    If people can't spell correctly in their own resume, they can't spell when programming, either.

    So? In coding, spelling consistently matters, not spelling correctly.

    And spelling correctly makes it a LOT easier to spell consistently. You don't get new people coming onto the project and starting to spell correctly because they don't know that the spelling is incorrect, and you don't get people who know that the spelling is incorrect typing it correctly then having to fix it.

  • (cs) in reply to kr00lis
    kr00lis:
    "Seeking a position (...) which will (...) in the pubic area".

    OMFG... I have to put this in... today!

  • (cs) in reply to some dude
    some dude:
    Uh, oh. I think we found Alvin. Either that or someone *seriously* forgot their <sarcasm> tags.

    No. You found the latest moronic troll, TopCod3r. If you search for other posts of TopCod3r, you'll see someone not near as smart or qualified as Alvin.

  • Claude Balls (unregistered) in reply to TheRubyWarlock
    TheRubyWarlock:
    The fact that "Alvin" didn't seem to comprehend basic programming concepts aside, I see no problem with looking things up like that. Any competent interviewer would understand that asking a "memorization" question is stupid when it comes to programming since one can easily find the answer. If anything, looking it up shows resourcefulness on behalf of the interviewee.

    I've admitted in the past that I'm not sure of the immediate answer to a question during a technical interview, followed by mentioning what I do know/remember relating to it, and the comment that I could easily use Google/MSDN/etc. or purchase a book and freshen up on the subject. If the interviewer holds that against me, then they're probably not something I wish to work with anyways.

    As an interviewer, I would certainly be moving on to the next candidate. If the questions are being asked, they are probably due to information or lack of information on your resume. I'd place your resume into the circular file immediately - do you know what that means, or would you like to google it, or refresh yourself on the topic?

  • Rich (unregistered) in reply to some dude
    some dude:
    Its obvious that Brent, having lacked experience in hiring developers, failed to accurately advertise the requirements for the position he was trying to fill. Now that he has gotten the wrong type of candidate, he's trying to cover up his own mistake by ripping on the applicant. .... Maybe Brent should go read some books on interviewing skills and not publicly ridicule applicants for his job posting. Its no wonder he can't hire anyone.

    Uh, oh. I think we found Alvin. Either that or someone seriously forgot their <sarcasm> tags.

    No, I think this really is irony (And not the Alanis version that someone was pushing above).

    Rich

  • (cs) in reply to TheRubyWarlock
    TheRubyWarlock:
    The fact that "Alvin" didn't seem to comprehend basic programming concepts aside, I see no problem with looking things up like that. Any competent interviewer would understand that asking a "memorization" question is stupid when it comes to programming since one can easily find the answer. If anything, looking it up shows resourcefulness on behalf of the interviewee.

    I've admitted in the past that I'm not sure of the immediate answer to a question during a technical interview, followed by mentioning what I do know/remember relating to it, and the comment that I could easily use Google/MSDN/etc. or purchase a book and freshen up on the subject. If the interviewer holds that against me, then they're probably not something I wish to work with anyways.

    There's a big difference in being able to answer simple technical questions or not.

    I work primarily in Delphi. Two frequently used classes are TList (basically a double-linked list with built in sort and search functionality), and a TStrings (a TList with the ability to store both a string and optionally an object associated with the string, based on TList). Both of these classes are used extensively by Delphi's Visual Component Library (VCL, or GUI controls) and RTL code. For example, the items in a listbox are held in a TStrings descendent, as are the items in a combobox, the lines in a multi-line edit control, etc. So anyone who's done any kind of GUI work in Delphi should be familiar with the basics of TStrings, like finding the number of items in a combobox (ComboBox.Items.Count) or the position of a string in the combobox (ComboBox.Items.IndexOf(stringToFind)). The guy I mentioned first in my previous post couldn't answer either of those questions.

    I asked the second guy from my previous post to explain the difference between a TList and a TStringList (a TStrings descendent for holding lists of strings or the contents of a text file, for example). The response? "TList holds a list of stuff. TStringList holds a list of other stuff." Hire? I don't think so.

    Granted, a good developer doesn't have to (in fact, can't) know everything, and should know where to find the answers they need in order to get the job done. However, even a mildly capable developer should know the basics. If they don't, they're not even mildly capable.

  • (cs) in reply to Claude Balls
    Claude Balls:
    As an interviewer, I would certainly be moving on to the next candidate. If the questions are being asked, they are probably due to information or lack of information on your resume. I'd place your resume into the circular file immediately - do you know what that means, or would you like to google it, or refresh yourself on the topic?

    If you notice, in my post I was not referring to the specific "Alvin" person since yes, what a static class is and managed/unmanaged code should be basic knowledge. I wouldn't hire someone like that, either.

    But you sound like exactly the kind of idiot, self-righteous manager who only looks for specific buzzwords and ignores everything else. God forbid someone not have everything about every programming language memorized. In this day and age nobody SHOULD have an entire language memorized, and the REAL WTF are idiots like you who think it's okay to ask stringent memorization questions and judge a candidate's worth based on them regurgitating canned answers.

  • mr_ed (unregistered) in reply to Diamonds
    Diamonds:
    I would have asked what keyword do you use to create a 'goatse' class. ... PS: Don't google that word.

    No, no. I think that you should definitely look up that word. ;)

    ROTFL

Leave a comment on “We'll Be In Touch Maybe”

Log In or post as a guest

Replying to comment #148465:

« Return to Article