Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I'll respond to your second point first, about withholding the code: you are responding to someone else's comment. I have not problem with people withholding their code. Sure, it might make things easier, but whether they do or not is really up to them. Some questions do not even need example code. If I need some, I will ask.

As to the first point,

That seems like a terribly unfair assumption. There are many people who can craft good useful code who can't write worth a damn. You shouldn't penalize them for it, especially considering how many developers speak English as a second language.
I don't think I am penalizing them, I am just going on the assumption that coding takes attention to detail, and writing a question does as well. There are differnces between bad questions, good questions, and questions written by people with English as a second language:

  • What are all command line options? Why do some of them not work for me?
  • Why does "perl -v" not show the current version when I type it at the command line? "perl -V" seems to work fine....
  • "perl -v" shows me errors, "perl -V" work fine?

I'm naturally going to assume the latter two people are slightly better at writing code, and at a more advanced level, than the first one.

In general, it's better to err on the side of assuming the questioner does not know very much, for these reasons:

  • It's better to explain something that they already know and risk a little "I knew that!" than to talk over their heads.
  • Other people reading your answer may not be as knowledgable as the original questioner and may learn something from your response.

In reply to RE: RE: RE: XYZ Questions by turnstep
in thread XYZ Questions by chromatic

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others musing on the Monastery: (2)
    As of 2018-02-19 22:26 GMT
    Find Nodes?
      Voting Booth?
      When it is dark outside I am happiest to see ...

      Results (266 votes). Check out past polls.