I seem to be "Pedantic About Good Programming Practices
Man" this morning, yet another super(?)hero that nobody
really wants to see:
So explain that you'll change the overall architecture
to accomidate new features, but you'll copy the individual
functions (or the algorithm part, if you're adding
arguments and making them members, but the keep it simple
for the boss) over from the original work, and reviewing
each as you go.
Don't forget the regression tests. There's little more
embarassing than refactoring a program "to improve its
robustness", then breaking the code in various subtle ways
that slip into production. Properly written regression
tests let you say to your manager: "So it works the way it
did before, and also does foo, and I can add new
features in half the time" with some actual data to back
you up.
See also How You (Yes You!) Can Get Involved and The Joy of Test, among
others.
--
The hell with paco, vote for Erudil!
:wq
-
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.
|
