[akanevsky]

amikhar, you are basically correct.

However, I cannot recall - when did I say that the "comittee" is not willing to give others to suggestions? Once the hack is published, we will give people suggestions on how to imporve their codes. Once the codes are perfected, they will be marked as "PHP Valid". This is still a team effort, isn't it?

People do not read instructions only because those instructions are poorly formatted and/or badly organized. Sometimes it takes a lot of energy just to read one post of instructions, because it is all messed up. Hack Manual Generator, by the way, was an attempt to solve this. I'd like to note that it was a successful attempt. Because of a good first post organization, my hack threads rarely contain "bug!" exclamations and/or questions about something that was already explicitly stated in the first post. Which is also true about threads of other coders, who took their time to write a neatly organized instructions post.

Now, about the more social way: nobody is going to learn unless they have a motivation to do so. In this case, the motivation would be the QA Team and its "PHP Valid" label. Which shouldn't necessarily stick out, it could be just a small label... For those who are interested.