note
talexb
<p>Disagree.</p>
<p>Those PITA warning messages are little hints that the craftmanship of the code is below par. Perhaps one in a thousand warnings can be ignored. The other 999 need to be addressed. An example.</p>
<p>Yesterday and today I had to write quick scripts to get some stuff done on a Production system. Normally I'd do a one-liner or cobble something absolutely horrible together, cross my fingers and go with it.</p>
<p>Instead, I wrote POD, used [cpan://Getopt::Long] to handle arguments, used <code>or die $usefulMessage</code> in all of the appropriate places. Yes, it took a little longer to write, and I tested as I went .. but the result was that these little utilities worked absolutely fine. Then what?</p>
<p>Then I checked them into our version control system so that I would know where to find them the next time I needed them. So now I have documented, commented, error checking utilities that I can pull out of my hat (so to speak) the next time we need to do X.</p>
<p>It all comes down to a matter of craftmanship. If my scripts and modules compile 100% clean, if I never have errors in my error logs, that's a sweet way to be.</p>
<p>So fix your code -- banish all warnings!</p>
<div class="pmsig"><div class="pmsig-131279">
<p>Alex / [talexb] / Toronto</p>
<p><small>"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds</small></p>
</div></div>
482733
482829