in reply to w/Modules and w/o Modules

How good is the test coverage of the code you've written?

Have you read in copious detail the documentation of the file formats you're handling?

How long have you been programming in any language?

How do you know your code works?

Improve your skills with Modern Perl: the free book.

Replies are listed 'Best First'.
Re^2: w/Modules and w/o Modules
by roboticus (Chancellor) on Sep 20, 2011 at 19:17 UTC

    ...not to mention: How many more octagonal wheels does the world need?

    ...roboticus

    When your only tool is a hammer, all problems look like your thumb.

[reply]
Re^2: w/Modules and w/o Modules
by Jeri (Scribe) on Sep 20, 2011 at 19:23 UTC

    These questions are reasons as to why I should use a module? Maybe the better question would be, when should I not use a module?

[reply]
      when should I not use a module?

      When your own code is better than the module, and when it's not worth your time to create and maintain your own code instead of using the module.

      Improve your skills with Modern Perl: the free book.

[reply]

        ...or when there isn't a module that does what you want...

        ...or it doesn't install and it takes you longer to try to figure out how the module works or isn't working rather than writing it yourself...

        ...or when you're confined to an old version of Perl that doesn't support the module you might've used...

        In my case, since I cannot directly attach to CPAN from my dev machine, if modules have a lot of dependencies, I find the install hassle to be a pain... as I have to dl it on one machine, burn it to a disk, then install it by hand on my dev machine...

        Of course when there is a module that does what I want, and it works and I don't have to implement it myself, I cry tears of joy... :)

[reply]

In Section Seekers of Perl Wisdom