Re: When is it better to NOT release a new module?

Replies are listed 'Best First'.
Re^2: When is it better to NOT release a new module? by tirwhan (Abbot) on Nov 02, 2005 at 18:24 UTC
When you can't handle criticism of your work. Or the incessant flood of thank-you notes, patches, donations and offers of employment that invariably follow the release of a CPAN module.	[reply]
Re^3: When is it better to NOT release a new module? by Aristotle (Chancellor) on Nov 02, 2005 at 20:51 UTC
The occasional offer of reproductive duties makes the flood worth sifting through, though. `;-)` Makeshifts last the longest.	[reply]
Re^4: When is it better to NOT release a new module? by Fletch (Bishop) on Nov 02, 2005 at 21:37 UTC
Only if you really like the smell of toner . . . (Oh, that kind of reproductive duties. Never mind.)	[reply]
Re^3: When is it better to NOT release a new module? by tilly (Archbishop) on Nov 02, 2005 at 22:40 UTC
I am trying to decide whether you're being naive or sarcastic.	[reply]
Re^4: When is it better to NOT release a new module? by tirwhan (Abbot) on Nov 03, 2005 at 07:07 UTC
Whimsical, I guess (sarcastic would imply that I'm denigrating the CPAN process). I am fully aware that there's a high probability none of these will follow a CPAN publication, though if the module is good and becomes popular, all of them may...eventually...possibly. Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan	[reply]
Re^4: When is it better to NOT release a new module? by Aristotle (Chancellor) on Nov 03, 2005 at 14:00 UTC
I think “incessant” is a pretty clear indicator of his tone, and “inevitably” only reinforces the impression… Makeshifts last the longest.	[reply]