After getting older, but not necessarily wiser, I've since learned what works best for me is to tell the user to "show me what it is
doing". This way, you're not admitting anything, nor are you denying anything.
A very sage piece of advice
I'm into my second decade of programming and engineering. And a few things still stand true:
the basic defect rate is still around one error per hundred lines of code.
Industrial strength testing and review will get about 99% of those, which means each year of coding I leave about one real bug. Somewhere.
Engineers are socially inept.
Conjugate buggy: my design is perfect; your design is interesting; his design is broken; their design is crap.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||
Others contemplating the Monastery:
(7)As of 2017-01-24 19:52 GMT