Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Comment on

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

I try to let people describe what goes wrong, and if possible, I ask question that the other one has to answer. Having error messages helps a lot, but even without, it can be doable. When debugging CGI applications over the phone, don't forget to ask about the error log. When you ask about error logs, don't ask for the last $few lines, but ask them to tail -f it, and read out loud what it says as the error occurs, and don't let them skip important things (with error messages, only the first one is important, as the other ones are probably results of something else being wrong).

When someone spells out c-h-o-m-p, I let them say every word as it is, and I complain about every word needlessly spelled out.

A problem I run into often is that people tend to forget dollars as they occur much. This is even more so if the person in question has no Perl experience. print $foo and print foo are not things you want pronounced equally.

I like it most when both ends have the same color-highlighting editor. That way I can ask for certain colors (namely those for comments and strings) to be ignored. (vim++ btw)

If you have e-mail or a fax, let them send code to you. It's a lot more efficient. If they can't, because the code is copyrighted, tell them that telling you the code is a violation too and that you have already written down everything he/she said.

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

In reply to Re: Debugging Perl over the phone by Juerd
in thread Debugging Perl over the phone by thelenm

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 romping around the Monastery: (6)
    As of 2018-06-21 05:43 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (117 votes). Check out past polls.