>>Just don't post your code to the list itself. It's rude to
>>bloat the mails on the list. Provide a hyperlink to your annotated code.
True, but what happens after you get your answer? You take the code down and
move on. It would be nice to have a place to post the code where it can be
organized and filed away with comments for future reference.
Also the idea would be more "code review" than "I have a problem". From my
perspective, I would like to see how others are solving problems and how
successful they were through a given solution. Maybe even have a moderating
system so that good code/comments float to the top ???
There are all kinds of bits and pieces of floating around the net and in
print: CPAN, O'Reilly books, Mailing list, etc. I can read perldocs to see
how a module is used, I can check out O'Reilly books for theory and simple
examples, and I can ask a mailing list for help when I get stuck, but
sometimes you don't know what module will help, you've read the O'Reilly
books and the examples are too simple/don't apply, and you aren't even sure
what question to ask the mailing list, what do you do? I bludgeon together
some code and hope that is good enough. I don't really have anyone to review
it and say "This is stupid".
I realize that you will probably have people do the cut and paste thing, but
if it's good code, is that really a problem - especially if there are
comments, etc. and an explanation of how the code works/is supposed to work
from the author??? I see this as both a code resource and a review forum ...
Thoughts???
Dave Homsher
Webmaster,
MACtac IT
