Well, people also create a LOT of bad games (empty levels, no story, total ripoffs, etc.). But there are always some people that like it.
Completely different.
People creating crappy games are not setting out to teach others how to make crappy games. That's fine - they can make a game as good or as bad as they want, based on their preference and ability.
People creating tutorials ARE trying to teach others to do things the same way. So they should know what they're doing, and their way SHOULD be a good way to do it.
An example:
My pet peeve ... using parallel processes when you don't need to, and not adding Waits to them when you do use them.
If someone adds 100 parallel process events to a single map in their game because of a poorly thought out design, and it lags like crazy, that's their choice.
If they then write a tutorial that shows others how to accomplish something by adding 100 parallel process events to a single map, THAT'S a problem. Then we will start getting all these support threads created asking "why does my game run so slow?" and we'll have to help them troubleshoot to figure out why, and then we'll have to help them redesign the system to achieve the same thing WITHOUT using 100 parallel process events.
So what I'm saying is that they should know "best practices" before they start teaching others. You wouldn't want to learn how to ride a horse from someone who's never ridden a horse, or who's only been riding for a month and can barely stay in the saddle
:)
Not knowing ctrl+shift+f in the script editor would only be a problem if you were writing a tutorial on how to use the script editor, and including a section specifically teaching people how to use the "find" function.
On the other ... I'm sure I've gone to the Window help numerous times and not had an error. Now I have to remember to try it again when I get home.