I couldn't disagree more with the central point of the article: that newbies should only ask for help from expert programmers as a last resort.<p>An expert may be able to solve an issue in seconds that a might stump a newbie for weeks. Moreover, a newbie will learn much quicker if given guidance from an expert than if left to their own devices.<p>I have been in both situations, learning from experts and sharing my expertise with newbies. I have always been happy to help out others and have certainly been shown the same helpfulness by people more expert than me.
I only ever do ask one question in an inverview. I decsribe a simple application and then ask the candidate to design the database schema and business objects to support it. That usually takes up the time I'm given with the candidate, and tells me a ton about what techniques and technologies they've been exposed to and their maturity level working with same. I also watch for how willing they are to involve me in the process. The best team candidates have me working along side them (but then I get to toss in a few curve balls)
I would ask "What are we looking for?"
A correct answer requires great insight and pretty much compels the candidate to continue and explain how they fit the description.
"Can you please teach me something?"<p>I only use it when I'm interested in the candidate, and the interview has progressed to the point where we're both comfortable.
OP's one question would not be my one question, which would be:<p>"What would be different here in one year because of your presence?"<p>Their approach, as well as their response, would teach me a lot about them.