A couple of weeks ago I wrote a post “7 C# Interview Questions to Weed out Losers” which was my most popular post yet. As of this writing, it has received over 13,000 views. It also got a lot of comments.
While there are a lot of things I could respond to, the one I want to focus on today is what I would call, “The fallacy of concepts over terminology.”
While none of the comments actually come out and say this, several imply that knowing the concept but not knowing the proper term for it is enough. In conversations with people I’ve worked with, I’ve received similar feedback. In fact, as recent as three years ago I actually told someone, “If you want someone who can pass some sort of test, I’m probably not your guy. If you want someone who is an awesome programmer, I’m your guy.”
But three more years of experience has changed my mind. Continue reading “5 Reasons Learning Terminology Increases Your Effectiveness [As A Programmer]”
Last week, I posted 7 interview questions for C# programmers. I guess I forgot that people can’t see in my brain. So, let me be very explicit this time. The “weed out the losers” questions are meant to do just that. Weed out people who have absolutely no business even applying for the job.
You would be amazed at how many people interview for a job who have all kinds of cool buzzwords on their resume, but when you ask them about it, they know nothing about the subject. I’m not sure if this is the recruiter who is representing them trying to help them out by beefing up the resume to get them in the door or if they actually do this themselves. But, as someone who interviews, I have to have a way of making sure the applicant I’m interviewing is worth interviewing in the first place. Hopefully, I can do this over the phone in less than a half an hour.
So, with that said, if your favorite question isn’t on this list, it is probably because it is a question I would save for some future interview.
Also, to those of you who may think that a technical interview doesn’t really tell you if the programmer is a good programmer or not, I have this to say…
You are right. And when I was a younger programmer and was being interviewed with technical questions, I felt the same way. But now that I’m on the other side of the table, I find that way too often, the people who can pass a technical interview are a lot more likely to be good programmers than the ones who can’t.
And finally, I would not rule out an applicant because he got a couple of questions wrong, or didn’t answer them exactly the way I expected. But if couldn’t answer most of them, that would raise a huge red flag!
So, once again, the place I am currently working has been interviewing for some more programmers and we’ve had to laugh at some of the answers we’ve received on some pretty simple question.
And that naturally got us all talking about good interview questions. How can we tell that the applicant is even worth interviewing?
The following questions are not meant to be THE interview. The questions are meant to shorten the interview process by ensuring the applicant has a basic understanding of the language they will be expected to work with.
Continue reading “7 C# Interview Questions [That Weed Out The Losers!]”
I got a question this last week that I answered very briefly but I felt that to answer it completely would take a blog post. So here’s the blog post.
Should the author of a piece of code be responsible for more than just unit testing, or does peer review have a play?
Continue reading “15 Ways To Write Beautiful Code [That Have Nothing To Do With Testing]”