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
See also How You (Yes You!) Can Get Involved and The Joy of Test, among
The hell with paco, vote for Erudil!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||