I agree, it depends.
Considering one case where a new perl programmer has a good understanding of all the abstraction is replacing, things are likely fine, aren't they? For example, could they likely code it without the abstraction so it works, albeit not as cleanly and with more effort?
Perhaps the coding requirement above isn't needed. If the programmer clearly understands all the things that are happening using the abstraction, maybe things are fine without learning the details.
As I learned recently, sometimes a cost in using the abstraction isn't noticed initially. A c program called by a script ended up needing considerable memory.
So, many considerations exist.
- Does they understand what exactly is happening?
- Are they any costs (i.e. time, memory) that should be avoided?
- Is the task being overly simplified or wrongly performed due to use of the abstraction?
It's very late, so I'd best leave continuing this list to my fellow monks.
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.