comment on

Here's a few home truths about rules.

Not all 'rules' were invented by people who knew enough to be defining rules.

Not all advocates of 'rules' know why they are advocating the rules they advocate.

Many 'rules' have very limited application; and not all adherents understand the limitations.

People learn and grow best by making the own mistakes.

If you always follow the 'rules', you never learn anything.

Give me a programmer who goes out on a limb occasionally and learns from the experience, and I'll show you someone who will be making the rules a few years from now.

Those who always seek a CPAN solution, and never look at the source of the solutions they choose, and never evaluate (perform their own benchmarks, tests, or mindwork exercises on those CPAN implementations), are the same people that will always be screaming for yet bigger, faster, more powerful hardware.

Not everything on CPAN is well written.

Not every task requires the complexity of the "perfect solution".

Not every task is worthy of the expense of the "perfect solution".

Databases are not magic.

Primarily, A programmer never gains good experience; never improves; never evolves; if they always take the easy route; always use someone elses code; always follow the rules.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: Breaking The Rules by BrowserUk
in thread Breaking The Rules by Limbic~Region

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks