You've been down-voted, but you're absolutely correct in some situations. Sure, answering those questions with "this is a great opportunity to learn how to rea

You've been down-voted, but you're absolutely correct in some situations. Sure, answering those questions with "this is a great opportunity to learn how to read the documentation" is the "right" response. But I think we've all experienced the frustration of trying to write something in a language we don't use every day, and 'wasting' our time looking up simple things ("okay, what's the exact syntax of a for-loop in this language again?") that just adds friction when we're trying to solve a problem. There's a reason programmers complain so much about being interrupted. Part of being a good teacher is being able to make those points of friction disappear and enable your students to "get it" and experience the joy of solving a problem. Don't let perfect be the enemy of good. How many kids would play football/soccer if you were only allowed to play a match with regulation numbers of players on each side, and stopping play every time someone didn't have 'perfect' form?