<?xml version="1.0" encoding="windows-1252"?>
<node id="488850" title="Re^3: Perl Best Practices book: is this one a best practice or a dodgy practice?" created="2005-09-03 00:38:33" updated="2005-09-02 20:38:33">
<type id="11">
note</type>
<author id="107600">
TheDamian</author>
<data>
<field name="doctext">
&lt;blockquote&gt;&lt;i&gt;
It is kind of far-fetched to talk about testing here.
&lt;/i&gt;&lt;/blockquote&gt;

Hmmmmm. Maybe I didn't make the smiley big enough. Let's try again:

&lt;blockquote&gt;
guess it's just as well that Chapter 18 suggests testing everything before you deploy it! &lt;font size="+4"&gt;&lt;tt&gt;;-)&lt;/tt&gt;&lt;/font&gt;
&lt;/blockquote&gt;

The point I was trying to make is &lt;em&gt;not&lt;/em&gt; that you should rely on the testing to catch this problem, but that, if you don't catch the problem earlier, the testing phase should still do so. 

&lt;p&gt;In other words, (just exactly as you say) best practices ought to be an integrated process, so even if one practice introduces a problem, another practice should catch it. Which is precisely what my book advocates.</field>
<field name="root_node">
488824</field>
<field name="parent_node">
488842</field>
</data>
</node>
