comment on

I have a recent personal experience of this.

Half a year ago, I did some intricate mangling of a query language. The delivery schedule was really, really tight.

People reading my code, complained that all the comments made it hard to read. That was a first. :-)

With less time pressure I would generally refactor code this complex, so it wouldn't need all the explanations. (Not so "clever" -- more "dense". Just an OO interface to the code's internal data structures would have helped a lot with clarity.)

The code more or less followed Perl Best Practices, but was still an example on how not to do it... :-(

Edit: Refactored this comment a bit, so it is possible to parse. :-)

In reply to Re^2: "Cleverness" from HOP by BerntB
in thread "Cleverness" from HOP by Wiggins

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.


Do you know where your variables are?
	PerlMonks