Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re^3: Perl Best Practices book: is this one a best practice or a dodgy practice?

by TheDamian (Vicar)
on Sep 03, 2005 at 04:38 UTC ( [id://488850]=note: print w/replies, xml ) Need Help??


in reply to Re^2: Perl Best Practices book: is this one a best practice or a dodgy practice?
in thread Perl Best Practices book: is this one a best practice or a dodgy practice?

It is kind of far-fetched to talk about testing here.
Hmmmmm. Maybe I didn't make the smiley big enough. Let's try again:
guess it's just as well that Chapter 18 suggests testing everything before you deploy it! ;-)
The point I was trying to make is not 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.

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.

  • Comment on Re^3: Perl Best Practices book: is this one a best practice or a dodgy practice?

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://488850]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others musing on the Monastery: (4)
As of 2024-04-23 23:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found