Randal L. Schwartz wrote:
This is what makes me trustworthy here. If you want this kind of respect, do the same: if you've actually *tested* a solution, say so. If you haven't tested it, ask yourself if you want your trustworthiness tested instead. :) And if not, say, "I *think*..."
True but I don't think one simple statement is enough. Back when I was just starting someone told me how to talk to the press: you say one thing, you say only one thing, and you say it over and over; then they might get it right...but don't bet the farm on it.
If you post untested code, clearly say so, both before and after it. Repeat what you're saying, over and over.
(And I'm not betting if anyone understand this. :) -- Just my 0.00000002 million dollars worth, Shawn Programming is as much about organization and communication as it is about coding. I like Perl; it's the only language where you can bless your thingy. -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
