Well, it's the concepts of "specialization" and "localization". You create an expert in the field of cookie jars and have that expert be the only person who knows how to handle cookie jars. That way, you can pretty much guarantee that no-one's going to screw up the cookie jar because they didn't know the correct way to get a cookie out while three other people are trying to do so as well.
As for slowing things down ... which do you prefer - "slow and correct" or "fast and wrong"? Except, "fast and wrong" is usually "runs fast, is wrong, and took way too long to write", while "slow and correct" is more often than not "runs fast enough, is provably correct, and came in ahead of schedule". I know which one I prefer ...
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
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.