I think they're stupid too. Going into an interview is already stressful enough and these types of questions don't put me into "problem solving" mode. They put me into "brain teaser" mode which is a different type of thinking for me. You know how we nailed these questions when I was in uni? We traded them after our interviews between each other and you just had to pretend you've never heard it before. So the main thing people were testing was whether or not the question had made it to them.

For programming, there are so many better ways to test out of the box thinking to me ... I think the "what happens when you press a letter into a web browser address bar" or something is better and at least relevant. One that I like is, "there's an outage in production, how would you go about diagnosing it?" Then as an interviewer I'd reshape the scenario and see where they put their focus and where they give up.