Yeah, in my experience teenagers (especially those that are highly self-motivated) can see stack traces and stuff as just another part of the puzzle. It's the

Yeah, in my experience teenagers (especially those that are highly self-motivated) can see stack traces and stuff as just another part of the puzzle. It's the younger and less motivated kids that tend to get frustrated. Edit: I'll also point out this: > It was pretty obvious to me that I had committed a mistake at some point of my code. How a student handles this is also often a sticking point. "Oh no, another error, I'm bad at this, maybe this isn't for me." Is an attitude that I've had to turn around. It goes a long way to convince a kid that it's actually the computer's fault because it isn't smart enough to understand what you're trying to tell it. So you have to be really specific in how you write to it. Then suddenly error messages are informative clues on the way to making your program work, rather than the computer scolding you for being a bad coder.