If you happen to be hit by a bus, chances are that no matter
how clearly and completely you write the text of your
documentation, an emergency situation will come up before
your (hopefully more bus-resistant replacement) will be
able to read it all.
That isn't to say that you shouldn't bother writing it... By
all means, you should.
I'm a strong proponent of application flow diagrams. In a
pinch, it's much easier to see which other things the
little picture of 'sqldb19' has lines running to, than to
scan through pages of text, hoping that you don't miss a
reference to 'sqldb10-20.'
Note that sqldb19 doesn't need to be a seperate server for
this to work. I apply this type of graphical overview to
things like cron jobs that summarize data, to be able to know
which reports will be wrong if suddenly the cron jobs all
stop. It's easy to trace the lines to the sql server, then
to the web servers that query it.
Eh, I tend to be pretty visual, so maybe this is just me...
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.