Actually most of what you are putting them down for is
actually good advice. I likewise use few comments, use
descriptive variable names, comment each function, etc.
If you are relying on understanding comments rather than
figuring out the code, you will have serious problems
when the two disagree. And they will come to disagree
over time - a general principle is that whenever two
things need to stay in sync (eg comments and code, code in
two places, etc) they inevitably will tend to not do so
perfectly.
The real problem sounds like the use of global
variables and a cut-and-paste methodology...
For the record the single most miserable piece of code that
I have had the misfortune to meet was also one of the
most straightforward and heavily commented. It was utterly
impenetrable for the same reason that legalese is so hard
to read.
-
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.
|
