Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • In principle I agree completely.

    I rarely code for clients to the same standard I code for CPAN.

    Or at least, I CODE for them as well if they are paying for me to be their "expert", but I often let some of the more finely detailed testing slip, and often let the API documentation slip.

    On CPAN, documentation is MUCH more important than for clients. Lots of comments for maintainers are still useful, but spending as much time on writing the POD as you spend writing the code (as you might for CPAN) just isn't worth it when there's an audience of MAYBE one.

    Beyond that I think it's important for developers to learn early what is serious infrastructure work (done at a CPAN-like level of quality) and what is work that you'd be willing to throw away if you have to.

    And you can mistakes if you get it wrong in both directions.

    My only big stumbling block these days is trying to work out which is which, and how to deal with the cases somewhere in between. And then how do you write a set of guidelines to help you demonstrate to others how to make similar decisions...