As usual, one of my favorite books
The Pragmatic Programmer
has some smart words to say about this. Check out "The Cat
Ate My Source Code" in Chapter 1, which provides the tip:
"Provide Options, Don't Make Lame Excuses." (There's also
a funny anecdote elsewhere in the book about a programmer
becoming convinced that the OS function select
must be broken, because his code, of course,
worked perfectly.)
I find it important to remember from time to time
that my job involves building software for people,
and if person after person doesn't understand what
I'm doing or what I've produced then the problem is
more likely to be with me, not everyone else.
Chris
M-x auto-bs-mode
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, details, 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, summary, 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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.