Is there a point beyond which layers of abstraction are a bad thing for new Perl programmers? Take, for example Class::DBI. Is it a good idea to teach new programmers the use of this module rather than DBI + SQL, considering they might not learn how Perl connects with the database if abstraction intervenes too soon? I can see the point of going straight in with CGI.pm since it takes care of some very gory details but I'm not sure about others. As abstraction becomes more sophisticated it certainly aids productivity but shouldn't we also consider what is lost, ie. a root connection with core Perl code? With some modules, such as Maypole for example, aren't we in danger of becomeing Maypole programmers rather than Perl programmers?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||