Front page | perl.beginners |
Postings from August 2009
Uri Guttman wrote: >>>>>> "I" == Ian <pcs305@gmail.com> writes: > > I> Unfortunately I'm not an expert. I just read a few books and this list etc. > > a couple of things. it is good that you are offering to help but as you > claim not to be an expert, it can hurt more than help. there are plenty > of experts on this list who can help and fixing up weak code offered > from beginners makes our work even harder. feel free to jump in with > ideas and questions but until you are sure of your skills, it is best to > not offer coding solutions. > > secondly, please don't top post. you are quoting the entire previous > post below your email. google for top posting and you will learn why > this is a bad (if prevalent) email style. Just want to elaborate with specifics in conjunction with Uri's post. For those who frequent mail lists and don't read the List Charter (if the list has one), here are a few links to common rules (they are dated, but most certainly still apply). Having proper email list etiquette is certain to provide the "old timers" (for lack of better terms) with much more incentive to peruse your post, as they will be better equipped to quickly grab out what they need, and analyze whether they want to contemplate reading the rest of the post [0]. Not following the 'standards' is *guaranteed* to cause people frustration. http://www.river.com/users/share/etiquette/ http://www.lemis.com/email.html http://www.lemis.com/email/email-rfc.html http://www.faqs.org/rfcs/rfc2646.html A quote by Randy Bush: A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? Steve [0]: I'm not stating that I'm any where near perfect, but I try in my posts. I also have a habit of leaving poorly formatted threads, unless my interest level outweighs the pain of reading.Thread Previous | Thread Next