If you're that worried about your replacement not being able to understand your code, either change the code or comment the bejesus out of it. Or more accurately, change the code or not as you see fit AND comment the bejesus out of it.
My own preference is toward simpler to understand rather than 'elegant' code - mostly because I'm only a casual programmer. Still, with sufficient comments (and a couple of reference books) I've always been able to understand what's going on in a piece of code. You can be as elegant / beautiful / complex / obtuse as you want to be IF you have sufficient comments in your code to make clear what you're doing.
Jack
-
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.
|