Why a certain company's recruitment team sucks today
-
About 5 years ago I used to work as a Perl programmer. I was a decent one and I enjoyed it. Since then, though, the industry has largely moved on and I've spent time working in PHP and then .NET. I now find myself needing to find a new job and last week applied for a job programming Perl. They sent me a technical test to do involving writing about half a dozen scripts to perform various small tasks, so I dusted off my Perl skills and set to work. I produced a set of scripts that were (I believe) neat, tidy, efficient, well-commented and which worked. Granted my Perl is rusty after 5 years but they all worked and worked well. Today I've received feedback from them, rejecting me, stating that "[you have] demonstrated that you understand some of the coding principals we are looking for, however some of the scripts seem to take coding styles from other languages?". As I said, the code was neat, legible and well-commented so I can only assume that this has counted against me for a Perl job. I didn't want the job anyway but I find it mildly ridiculous to say the least and frankly slightly insulting.
-
Dan_Martin wrote:
some of the scripts seem to take coding styles from other languages?
In what is this a bad thing ? What is a "coding style" anyway ?
I'm really not sure. I know there are Perl programmers out there who delight in producing obfuscated code that takes up as few lines as possible but I've always preferred to write programs that are clear and easy to understand. I guess that means I'm no Perl guru. Oh well.
-
I'm really not sure. I know there are Perl programmers out there who delight in producing obfuscated code that takes up as few lines as possible but I've always preferred to write programs that are clear and easy to understand. I guess that means I'm no Perl guru. Oh well.
-
I'm really not sure. I know there are Perl programmers out there who delight in producing obfuscated code that takes up as few lines as possible but I've always preferred to write programs that are clear and easy to understand. I guess that means I'm no Perl guru. Oh well.
Dan_Martin wrote:
I know there are Perl programmers out there who delight in producing obfuscated code that takes up as few lines as possible but I've always preferred to write programs that are clear and easy to understand. I guess that means I'm no Perl guru.
I know people who can write complete sentences on codeproject forums in only a few letters (yes rly :laugh: ). But that doesn't make one a language guru. Be happy you didn't get the job. If the recruitment team has that kind of attitude, only imagine what people you would be working with. Don't give up searching, you'll find a job you will like.
-
About 5 years ago I used to work as a Perl programmer. I was a decent one and I enjoyed it. Since then, though, the industry has largely moved on and I've spent time working in PHP and then .NET. I now find myself needing to find a new job and last week applied for a job programming Perl. They sent me a technical test to do involving writing about half a dozen scripts to perform various small tasks, so I dusted off my Perl skills and set to work. I produced a set of scripts that were (I believe) neat, tidy, efficient, well-commented and which worked. Granted my Perl is rusty after 5 years but they all worked and worked well. Today I've received feedback from them, rejecting me, stating that "[you have] demonstrated that you understand some of the coding principals we are looking for, however some of the scripts seem to take coding styles from other languages?". As I said, the code was neat, legible and well-commented so I can only assume that this has counted against me for a Perl job. I didn't want the job anyway but I find it mildly ridiculous to say the least and frankly slightly insulting.
Want me to write up an appropriate response for you? :)
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
About 5 years ago I used to work as a Perl programmer. I was a decent one and I enjoyed it. Since then, though, the industry has largely moved on and I've spent time working in PHP and then .NET. I now find myself needing to find a new job and last week applied for a job programming Perl. They sent me a technical test to do involving writing about half a dozen scripts to perform various small tasks, so I dusted off my Perl skills and set to work. I produced a set of scripts that were (I believe) neat, tidy, efficient, well-commented and which worked. Granted my Perl is rusty after 5 years but they all worked and worked well. Today I've received feedback from them, rejecting me, stating that "[you have] demonstrated that you understand some of the coding principals we are looking for, however some of the scripts seem to take coding styles from other languages?". As I said, the code was neat, legible and well-commented so I can only assume that this has counted against me for a Perl job. I didn't want the job anyway but I find it mildly ridiculous to say the least and frankly slightly insulting.
Knowing a few perl programmers I'll highlight the issues:
Dan_Martin wrote:
I produced a set of scripts that were (I believe) neat, tidy, efficient, well-commented and which worked.
You should have written it all in one line, using single letter variable names, and made sure to put in a few error conditions 'which will never happen'. That or they were just looking for a reason to blow you off. I'd consider contacting them for more specific feedback myself.
-
Want me to write up an appropriate response for you? :)
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Now, there's an idea. Maybe you could moonlight as an HR consultant here at CP. It could become legendary in short order. :-D
L u n a t i c F r i n g e
As well received as my letter to Michele was yesterday, I think you might be onto something.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
As well received as my letter to Michele was yesterday, I think you might be onto something.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
About 5 years ago I used to work as a Perl programmer. I was a decent one and I enjoyed it. Since then, though, the industry has largely moved on and I've spent time working in PHP and then .NET. I now find myself needing to find a new job and last week applied for a job programming Perl. They sent me a technical test to do involving writing about half a dozen scripts to perform various small tasks, so I dusted off my Perl skills and set to work. I produced a set of scripts that were (I believe) neat, tidy, efficient, well-commented and which worked. Granted my Perl is rusty after 5 years but they all worked and worked well. Today I've received feedback from them, rejecting me, stating that "[you have] demonstrated that you understand some of the coding principals we are looking for, however some of the scripts seem to take coding styles from other languages?". As I said, the code was neat, legible and well-commented so I can only assume that this has counted against me for a Perl job. I didn't want the job anyway but I find it mildly ridiculous to say the least and frankly slightly insulting.
Here's a letter you can send them: Dear Mr 'tard, I've been writing code in multiple disciplines for many many years, and try to apply my vast accumulated knowledge to every script or program that I write. The most important thing to remember about programming is to perform the specified operation as efficiently as possible, and finish the assigned task on time (often dictated by requirements and time alloted to the task). This means that someone else's idea of "sttyle" is completely irrelevant, and development pardigms are about as contextual as how you butter your toast. Beyond that, my code is copiously commented so that fuck-tard management types like yourself can actually have somewhat of a clue as to what's happening in the code so that you can report to even bigger fuck-tards that the situation is well in hand, and still look like you mean it. Now, I realize that not all management fuck-tards aren't able to comprehend what I just said, and you're probably one of them, so let me give you some advice that even someone with your limited intellect could understand... SHOVE YOUR JOB UP YOUR BLOATED ANAL PORE. You'll know you've shoved it far enough when you can feel it tickling your tonsils.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Here's a letter you can send them: Dear Mr 'tard, I've been writing code in multiple disciplines for many many years, and try to apply my vast accumulated knowledge to every script or program that I write. The most important thing to remember about programming is to perform the specified operation as efficiently as possible, and finish the assigned task on time (often dictated by requirements and time alloted to the task). This means that someone else's idea of "sttyle" is completely irrelevant, and development pardigms are about as contextual as how you butter your toast. Beyond that, my code is copiously commented so that fuck-tard management types like yourself can actually have somewhat of a clue as to what's happening in the code so that you can report to even bigger fuck-tards that the situation is well in hand, and still look like you mean it. Now, I realize that not all management fuck-tards aren't able to comprehend what I just said, and you're probably one of them, so let me give you some advice that even someone with your limited intellect could understand... SHOVE YOUR JOB UP YOUR BLOATED ANAL PORE. You'll know you've shoved it far enough when you can feel it tickling your tonsils.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Now i started to read this and thought this can't be JSOP, till i started reading the 4th sentence. the amount of abuse or swearing was limited till then. nearly thought JSOP's account was hijacked :laugh:
Marc Clifton wrote:
That has nothing to do with VB. - Oh crap. I just defended VB!
-
About 5 years ago I used to work as a Perl programmer. I was a decent one and I enjoyed it. Since then, though, the industry has largely moved on and I've spent time working in PHP and then .NET. I now find myself needing to find a new job and last week applied for a job programming Perl. They sent me a technical test to do involving writing about half a dozen scripts to perform various small tasks, so I dusted off my Perl skills and set to work. I produced a set of scripts that were (I believe) neat, tidy, efficient, well-commented and which worked. Granted my Perl is rusty after 5 years but they all worked and worked well. Today I've received feedback from them, rejecting me, stating that "[you have] demonstrated that you understand some of the coding principals we are looking for, however some of the scripts seem to take coding styles from other languages?". As I said, the code was neat, legible and well-commented so I can only assume that this has counted against me for a Perl job. I didn't want the job anyway but I find it mildly ridiculous to say the least and frankly slightly insulting.
Different companies have different way of doing things. While I'm not advocating them, at least they sent you a response and stated some reason for rejecting you (however silly that may be). :)
Workout progress:
Current arm size: 14.4in
Desired arm size: 18in
Next Target: 15.4in by Dec 2010Current training method: HIT
-
About 5 years ago I used to work as a Perl programmer. I was a decent one and I enjoyed it. Since then, though, the industry has largely moved on and I've spent time working in PHP and then .NET. I now find myself needing to find a new job and last week applied for a job programming Perl. They sent me a technical test to do involving writing about half a dozen scripts to perform various small tasks, so I dusted off my Perl skills and set to work. I produced a set of scripts that were (I believe) neat, tidy, efficient, well-commented and which worked. Granted my Perl is rusty after 5 years but they all worked and worked well. Today I've received feedback from them, rejecting me, stating that "[you have] demonstrated that you understand some of the coding principals we are looking for, however some of the scripts seem to take coding styles from other languages?". As I said, the code was neat, legible and well-commented so I can only assume that this has counted against me for a Perl job. I didn't want the job anyway but I find it mildly ridiculous to say the least and frankly slightly insulting.
Dan_Martin wrote:
They sent me a technical test to do involving writing about half a dozen scripts to perform various small tasks, so I dusted off my Perl skills and set to work.
Actually, all they really needed was those scripts, which you happily supplied, saving the company untold thousands of dollars in salary. ;P
-
About 5 years ago I used to work as a Perl programmer. I was a decent one and I enjoyed it. Since then, though, the industry has largely moved on and I've spent time working in PHP and then .NET. I now find myself needing to find a new job and last week applied for a job programming Perl. They sent me a technical test to do involving writing about half a dozen scripts to perform various small tasks, so I dusted off my Perl skills and set to work. I produced a set of scripts that were (I believe) neat, tidy, efficient, well-commented and which worked. Granted my Perl is rusty after 5 years but they all worked and worked well. Today I've received feedback from them, rejecting me, stating that "[you have] demonstrated that you understand some of the coding principals we are looking for, however some of the scripts seem to take coding styles from other languages?". As I said, the code was neat, legible and well-commented so I can only assume that this has counted against me for a Perl job. I didn't want the job anyway but I find it mildly ridiculous to say the least and frankly slightly insulting.
-
Now i started to read this and thought this can't be JSOP, till i started reading the 4th sentence. the amount of abuse or swearing was limited till then. nearly thought JSOP's account was hijacked :laugh:
Marc Clifton wrote:
That has nothing to do with VB. - Oh crap. I just defended VB!
Righteous indignation must be inserted at exactly the right point, or it loses its affect. and could diminish the finessed vitriolic nature of the response...
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Righteous indignation must be inserted at exactly the right point, or it loses its affect. and could diminish the finessed vitriolic nature of the response...
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Congrats, I don't recall having seen finessed and vitriolic used in the same sentence before, much less so elegantly...
-
Dan_Martin wrote:
some of the scripts seem to take coding styles from other languages?
In what is this a bad thing ? What is a "coding style" anyway ?
Rage wrote:
What is a "coding style" anyway ?
For HR? It's a sheet of paper with little bits cut out. They put it on top of your code, and if the expected words (they have a list) can't be seen through the holes, you haven't met their coding style requirements.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Want me to write up an appropriate response for you? :)
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001How many 'g's in "bang"?
I wanna be a eunuchs developer! Pass me a bread knife!
