It was Wednesday, December 01, 2004 when JupiterHost.Net took the soap box, 
saying:
: I also agree that lazy posters should maybe be handled a bit less 
: harshly lest we become the qmail list ;p

If anything this is my biggest complaint.

: In the case being discussed the code posted after it was recommended to 
: post some example code didn't even compile, which was more than being 
: lazy, it was causing even more work which is really frustrating...

Yes it is frustrating. I want to point out that my example answer did
show code and explain some simple concepts but I left one important
thing out. It was not code that could be copied and pasted as-is into
a file and run. I expected the person I was helping to either know how
to put it together or ask how to put it together. If the latter was
the case I would have expected to see the attempt. If I had not, I
would politely request to see the code afterwhich I would offer
further help.

Being extra nice with sugar on top is frustrating. It's often a
thankless task. But that's what this list is here for.

Discussing a problem in the abstract is okay. That is, without
code. If you want to see code, request it. Nicely.

  Casey West

-- 
Shooting yourself in the foot with AIX
You can shoot yourself in the foot with either a .38 or a .45.


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>


Reply via email to