Yet another reason I hate everyone in my profession

Because, truly, programmers are awful, awful people. Web developers are the worst, but I could be biased here, since I get exposed to more of them.

Anyhow. This article recently went up on Model View Culture. It's penned by a recent college grad whining that technical interviews are "bullshit." They are bullshit because they are confrontational, and they make women uncomfortable, and "There are so many questions that technical interviews can’t answer: Are they able to work on a diverse team? Are they passionate about the job they’re interviewing for? Can they read and debug pre-existing code? How quickly are they able to learn new technologies? Are they a jerk?"

Technical interviews, you see, require you to write code on a whiteboard, in front of people.
As a Crotchety Industry Veteran, if I was interviewing someone that struggled with the concept of writing code, they would be out the door so fucking fast their own personal universe would red-shift. I don't give two tugs of a dead dog's cock if you're a really nice person or get along well with others, or have a super-cute kitten calender for your office if you can't write code: You Do Not Get to be a Programmer.

These interviews exist because so many people can't fucking code. I have worked with these people. I have fired these people. They keep fucking applying to jobs that they cannot do. So Now: we have to check. If I hurt someone's feelings by expecting them to demonstrate the core skill for their job, I get warm fuzzy feelings all day long. You're a shitty test taker? The test is called Employment, and you just got an(other) F.

All code is awful. I don't care if someone writes a really ugly function on the spot, or if they forgot a semi-colon, I just need to know that this person does, in fact, know how to write code at all.
I know that this will sound insane to anyone in a real profession, but this is actually a serious problem that our young graduate above appears unaware of.  Go read that article, it is short, and it's about a very simple programming problem frequently used in "technical interviews." The interview-ee manages about 2 pages of crazy person scrawl before crashing and burning.

For reference, here's a solution in C#:

for(int x = 1; x <= 100; x++) {
 string output = "";
 if(x%3 == 0) output += "Fizz";
 if(x%5 == 0) output += "Buzz";
 if(output == "") output = x.ToString?();
 Console.WriteLine?(output);
}

For all I know, that interview-ee was a super-duper guy, and always buys a round for the team at the bar. The next time your computer crashes or app freezes? Think of that guy. Technical interviews are a Good Thing.