I agree with
Ovid's premise. Though it is not always true.
Sometimes the writer's energy for naming just failed or the
naming was just boggled somehow. Additionally
Ovid's
premise is just not true, if I have well designed code
and randomly change the identifiers I would have obfuscated,
well-designed code. I agree because
The physical medium in
which we construct programs is so facile that it behooves us
to construct programs whose models reconstruct in our and other minds easily.
Your point is also sublime. Thanks.
All of this side steps the issue of domain knowledge.
What is an EXPENSE_LIMIT? Is this terminology
which is standard to accounting, to accounting programs, an
unknown or forgotten
computer science snippet or
a construct named idiocyncraticly to this program/system?
<p>
This is also an issue to consider in the pursuit of clarity.
Update: Struck out text, respelled computor.
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.