note
FoxtrotUniform
<p>I seem to be "Pedantic About Good Programming Practices
Man" this morning, yet another super(?)hero that nobody
really wants to see:</p>
<ul>
<i>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.</i>
</ul>
<p>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 <i>foo</i>, and I can add new
features in half the time" with some actual data to back
you up.</p>
<p>See also [id://117895] and [id://158399], among
others.</p>
<p><tt>-- <br>
The hell with [paco], vote for [Erudil]!<br>
:wq</tt></p>
180103
180216