in reply to Re: Five Common Misconceptions While Learning Perl
in thread Five Common Misconceptions While Learning Perl
Using modules is only worth it if you're good enough at [Pp]erl to debug the flaws in someone else's module; this is usually even harder than debugging your own code.
And yes, modules can contain bugs. Heck, even the perl binary occasionally has bugs; the more code you can understand and fix yourself, the less you're held hostage to someone else's failings.
If you have the time to invest in understanding something directly, do it. Using a module is only a sound business decision if you can trust the author to have coded it right; otherwise you're setting yourself up for a pile of extra maintenance and bugfixes. Often, this involves reading and deciphering so much obfuscated module code that you might as well have coded it yourself, in a readible way, in the first place, and saved yourself the mental anguish of dealing with some foreigner's tortured notion of how to write decent English documentation.
In short, if you want the job done right, you get what you pay for. If you're not willing to code it yourself, you have to check it yourself, and that's not better. Ultimately, you're the one responsible for the solutions you provide, so if you can't guarantee them, you can't trust them.
Edited by planetscape - fixed the anonymonk's square brackets which were being linkified
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: Five Common Misconceptions While Learning Perl
by revdiablo (Prior) on Dec 01, 2005 at 23:34 UTC | |
by Anonymous Monk on Dec 02, 2005 at 20:31 UTC | |
by revdiablo (Prior) on Dec 02, 2005 at 21:15 UTC | |
Re^3: Five Common Misconceptions While Learning Perl
by Aristotle (Chancellor) on Dec 28, 2005 at 12:42 UTC |