During the Job Interview Challenge Series we are running here at Dev102.com, we usually get some comments from readers who think that the quality of a specific question is not good. Here are some of those comments:

1. “I hate interview questions like this, as it’s just a race to see who gets the a-ha moment first“.
2. “This is not a good interview question. What does it tell you about someone’s engineering ability? Little. It’s a brain-teaser; either you get it or you don’t”.
3. “Really enjoying the problems so far but I’m a little disappointed with this one. I prefer ‘thinking’ problems to ‘research’ ones“.
4. “Isn’t this an awfully language-specific question?“.
5. “If you presented this problem in an interview and made me an offer, I’d turn you down“.

On the other hand, many readers provided answers to the questions and enjoyed participating in those challenges. Some thought that the questions are very good:

Software errors, are so prevalent and so harmful that they cost the U.S. economy an estimated $59.5 billion annually. There are many examples of very serious and detrimental software errors such as:

• The Ariane 5, Explosion in 1996 (data conversion of a too large number).
• Mars Climate Orbiter in 1999 (Mixture of pounds and kilograms).
• Railway Signal Box Altona, Germany in 1995 (not enough memory).
• Radiation Deaths in 1985 (AECL Computer Errors).

Obviously, we would like to deliver a “bug free product” to our customers, but unfortunately, this is an un achievable goal. While some errors can be very easily eliminated, other are very evasive. What are the measures taken into consideration when we decide if an error is evasive or not? Lets create a list of software error parade and talk about it:

This one is for all you guys who are just starting to use LINQ and have no idea how to make those queries work.
I have tried it and i am glad to say that it is very friendly and usable especially if you have no experience with Linq
Linqpad is a very user friendly LINQ editor [...]