How To Find Bad Programmers
AmberShah writes "The job post is your potential programmer's first impression of your company, so make it count with these offputting features. There are plenty of articles about recruiting great developers, but what if you are only interested in the crappy ones?" I think much of the industry is already following these guidelines.
You want bad programmers? Start a MUD/MUX/MUSH and advertise for coders, you'll get the damned scum of the earth, a Mos Eisley cantina of crap coders
Step 1: Create an Ask Slashdot looking for (ironically) *good* programmers
Step 2: Identify all self-identified good programmers
Done!
You get what you pay for. You want a good coder? Look at their code. Make them take some written tests and an oral exam. Have them write you something small for free.
Hell yeah. That's why, when deciding whether a job is worth taking, I always ask the prospective employers to give me a month of salary without working for it.
There does seem to be an awful lot of shitty jobs out there, though.
No problem is insoluble in all conceivable circumstances.
That's what the roll of carpet and shovel is for...
Blank until
The really classy HR and Recruiter turds put down requirements for years of experience greater than the time the technology has been in existence. For developers, 16 years J2EE required! 10 years .NET a must! 8+ years Red Hat Enterprise Linux deployment!
Bonus points for confounding distribution release numbers and internal software version numbers, or assuming only RedHat distributes GNU/Linux.
Knowledge of 6+ OSes and at least 15 programming languages, developer experience in everything from industrial controls to web apps, etc. Hire the applicant who looks like he's fresh out of college. There's your bad programmer.
You have definitely come to the right place!
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
Interviewer: "Do you code exclusively in PHP?"
Answer: "Yup! Been using it ever since I gave up VB6."
Interviewer: "You're hired!"
The world's burning. Moped Jesus spotted on I50. Details at 11.
Bill? Is that you?
Some people here could fill that job!
And....
Okay, I have to write this to get past the lameness filter. But listing too many languages is likely to get you a very experienced engineer, not a bad programmer.
The society for a thought-free internet welcomes you.
Not cocky enough to be Good.
"I don't know, therefore Aliens" Wafflebox1
Well, you'll certainly get bad programmers if you choose the ones with 'C+' on their resume.
It's better to vote for what you want and not get it than to vote for what you don't want and get it.
- E. Debs
Listen, buddy, I don't know how you did it, but my company's lawyers will be contacting you shortly.
There is no way in hell you should have gotten a copy of our hiring procedure through any legitimate means, but if you did you had to have signed the NDA that came with it.
"This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
My favorite result from a recruiter - and this was an "in-house" recruiter, which are often the best - is this story. We were building a Windows appliance, so I was looking for a UI programmer with Windows experience and any kind of background with industrial automation or appliance UIs. Any experience with blade server management a plus.
I got resumes from guys who had done industrial automaiton for ... manufacturing window frames ... and turbine blades. There really is nothing going on in these guys' heads: it's just keyword matching, nothing more.
Socialism: a lie told by totalitarians and believed by fools.
Try asking for C, C#, C$, C%, C^ and C(.
I'm confused, what?