Felonious: "It's almost an automatic given that whenever you post a question about some code you've puzzled over for days, someone will point out that module X or project Y already does that, and say "Don't re-invent the wheel!". That's fine."
It's possible to search prior art as thoroughly as one can, not find anything, code and post, and still get a "Don't re-invent the wheel!" admonition. Sometimes, I think we don't know we've reinvented something. There are many modules (many of which are excellent), often under arcane names or we don't know the cannonical name for the thing we just reinvented ...
Felonious: "What better way to learn real programming than to actually do real programming, knowing you have a working example to refer to if you are stalemated by a problem? "
++Very true when someone's in 'student mode'. I'm a big believer in reinventing wheels when it's convenient, useful, or necessary to do. But when speed and/or certainty are at stake, it's probably a luxury at best, a costly boondoggle at worst.
jeffa: "True, but even if someone realises their problem has already been solved, they may not choose the best solution."
Many times, for neophyte to middle-skill coders, this is a real problem. There are other threads here about speculated rating (popularity or XP-like) systems for CPAN modules, PM-like comment threads attached to each module for other's to review, etc. I for one, would like some type of solution, at least like the PM discussion threads. Trying to choose among competing modules can be confusing and time wasting (see above:). When in unfamiliar territory I normally search with Google and at PM for module discussion when I'm having some difficulty choosing a module. It would be useful to have much of it in one place.
BUU: "Unless of course *gasp* you write a better solution..."
Absolutely, and a rating or discussion system that was maintained and managed as well as PM is would be outstanding, since many of us may not always know why one is better than another.(wow - Imagine trying to agree on the rating system validity) Ok, I recant - the rating system idea seems overly complex. I vote for multi-topic threaded discussions for each module...:)
Just my 0.02 meditation.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.