Call me lazy if you wish but I almost never want to program during the weekend. That time is better spent with family, or playing games, or washing the car. Or something. Anything really. If I come into work having burned my brain out over the weekend programming something, then I don't produce results that satisfy me. Hehe.
I follow up with questions about how they solved some difficult problem in their life (could be programming or could be just learning how to change their oil). I ask them how they came up with a solution and what they learned about it. I want to see if they learned enough from it to be able to explain it to me or anyone else in the interview.
Doing that gives me an idea of how their communication skills are. I want to gauge their problem solving and debugging skills during the interview, because I think almost anyone can be taught to be a better programmer, but it's much harder to learn to be an exceptional troubleshooter/problem solver and that tends to be a majority of what software developers do.