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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
