22 ms·

Standard Rule of Thumb: As soon as you can complete the "hello world" tutorial, you should add the language to your resume.

by rman666 14y ago

thirsteh 14y ago
If you want to work at a hipster company with no HR process. Most reputable companies will have someone who knows the most obscure languages you've listed interview you, and you will get owned. A better rule is to put a language on your resume when you can think of a question, and you immediately know how to approach (not solve) the problem using language X.
spiffage 14y ago
I disagree. When I'm interviewing, I take any line item on a candidate's resume as license to hammer them on their knowledge of that technology and its paradigms.
- waterlesscloud 14y ago
  Let me ask you something- What will you have achieved after you "hammer" them on that technology? Will you genuinely be closer to assessing whether that candidate can do the job you need done?
  - cafard 14y ago
    I am not a hammerer. Yet once when I saw PL/SQL on a candidate's resume, I did start asking some questions--not stuff like "explain PRAGMA WNDS" but "tell me a bit about how you've done xyz in PL/SQL" and promptly hit a blank look. I think that it is reasonable to ask questions about what is on a resume.
- finnw 14y ago
  About 6 years ago I was interviewed for a position that was (mostly) C++ coding. I told them I had been coding in C++ for four years. They said "So what level are you, Expert or Guru?" I thought it was a trick question, and replied that anyone who calls themselves an "expert" after less than 7 years or "guru" after less than 12, is probably over-representing their skill level. Unfortunately (1) they were serious, (2) what I said applied to all three of my interviewers and (3) it was an internal interview. I had to leave the company very soon afterward. My former boss insisted that I was at least as skilled (at coding) as those three (I passed the technical questions comfortably), and it was just my reluctance to self-promote that let me down. I don't regret it at all. I would not have done well in that culture, whether I had the coding skills or not. And I avoided having to move (1000s of miles.)
idbfs 14y ago
To those giving serious replies: I'm quite sure (rather, I hope!) the parent is being sarcastic.
viraptor 14y ago
Please don't do that... at some point you're going to run into someone interested in such language, which you can use only for "hello world". And he'll be happy to ask you all about it, in details.

Standard Rule of Thumb: As soon as you can complete the "hello world" tutorial, you should add the language to your resume.

by rman666 14y ago

Standard Rule of Thumb: As soon as you can complete the "hello world" tutorial, you should add the language to your resume.

thirsteh 14y ago

If you want to work at a hipster company with no HR process. Most reputable companies will have someone who knows the most obscure languages you've listed interview you, and you will get owned. A better rule is to put a language on your resume when you can think of a question, and you immediately know how to approach (not solve) the problem using language X.

spiffage 14y ago

I disagree. When I'm interviewing, I take any line item on a candidate's resume as license to hammer them on their knowledge of that technology and its paradigms.

waterlesscloud 14y ago
Let me ask you something- What will you have achieved after you "hammer" them on that technology? Will you genuinely be closer to assessing whether that candidate can do the job you need done?
- cafard 14y ago
  I am not a hammerer. Yet once when I saw PL/SQL on a candidate's resume, I did start asking some questions--not stuff like "explain PRAGMA WNDS" but "tell me a bit about how you've done xyz in PL/SQL" and promptly hit a blank look. I think that it is reasonable to ask questions about what is on a resume.
finnw 14y ago
About 6 years ago I was interviewed for a position that was (mostly) C++ coding. I told them I had been coding in C++ for four years. They said "So what level are you, Expert or Guru?" I thought it was a trick question, and replied that anyone who calls themselves an "expert" after less than 7 years or "guru" after less than 12, is probably over-representing their skill level. Unfortunately (1) they were serious, (2) what I said applied to all three of my interviewers and (3) it was an internal interview. I had to leave the company very soon afterward. My former boss insisted that I was at least as skilled (at coding) as those three (I passed the technical questions comfortably), and it was just my reluctance to self-promote that let me down. I don't regret it at all. I would not have done well in that culture, whether I had the coding skills or not. And I avoided having to move (1000s of miles.)

idbfs 14y ago

To those giving serious replies: I'm quite sure (rather, I hope!) the parent is being sarcastic.

viraptor 14y ago

Please don't do that... at some point you're going to run into someone interested in such language, which you can use only for "hello world". And he'll be happy to ask you all about it, in details.