Let me instead go over my interviewing. What I've decided is best is to find a way to get the candidate to talk, something that interests them. It doesn't really matter what as long as it is work related.
What I find is this is also hard. People don't go into an interview prepared to talk about their opinions and interests. If they did, they wouldn't be prepared for most interviews. I think this matches closely with your own code example, we don't need to see your history of learning, tell us about what you're proud of.
I don't like coding changes, I try not to use them, but I can understand how technical talks can be intimidating out of school.
I do use the code review portion, may include bug if hiring for a position where that seems appropriate but I've only been interviewing for SDET positions and does not seem useful yet.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.