in reply to Pedagogy: pointers or plaintext posts
I always try to find the answer for myself before I come looking for help. Hopefully most people do this. If they don't, they're not gonna learn anything anyways. Sometimes it's a matter of knowing where to look. Other times, the documentation is too long or too hard to understand. I've seen plenty of modules whose pod doesn't tell you anything.
For that reason, I like to give/receive both code and a reference. A picture's worth a thousand words, even if the picture's actually some code. This is especially comforting to newbies, who may need to have their hands held. However, the documentation will probably have other useful things in it, else that too would just be a code snippet. Remember, also, that resources like Ovid's CGI course are good references.
elusion : http://matt.diephouse.com
Update:
This is my 100th post.
|
|---|