Listen to the why's, and not the what's, and you'll hear judgement. In my experience this is very ill-advised. The answer to "why" questions varies so dramatic

Listen to the why's, and not the what's, and you'll hear judgement. In my experience this is very ill-advised. The answer to "why" questions varies so dramatically that it's extremely difficult to get an unbiased, realistic answer to those questions. I normally ask a bunch of "how" questions and eventually you unravel the "why". The questions presented sound good on paper but don't matriculate that way in person. For example: What's your least favorite part of Ruby and the Ruby on Rails framework, and why? Tell me about the last time you used an interesting bit of technology, and what you learned from it. Are much more naturally spoken as: How do you feel about your least favorite parts of Rails? How have you benefited from an interesting bit of tech? It's amazing how much more human responses become when you use the words "how" and "feel".