Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
" knowledge was about a week out of date..."

I find out-of-datedness less of a problem, as it will give you a sense of history in the end. Which will hopefully make you realize that all those nice things in Open Source didn't get there by itself, but were the result of hard work of countless, and often nameless, contributors. As long as it is clear which knowledge can be applied where (as in: in which version), I don't see a problem.

It will also make you realize that there is no "definitive" truth in programming (as anywhere else in the world for that matter). And that you should always verify. "Trust, but verify". There are even <plug>conferences</plug> about this.

Personally, I find that the combination of my 25 years experience in programming, combined with my programmers' laziness, tends to trip me up when I start making assumptions. Assumptions based on my experience, of course, but not necessarily having any foundation in "current" reality anymore. In that manner, I find the openness of Perl Monks, and the willingness to correct (in my case, mistakenly perceived) authority, refreshing.

So I can only concur with BrowserUk: "The only way I am ever going to know if what I think I know is correct is if people who know better correct me when I am wrong.

So please, correct me. I welcome your input. I may not directly accept it at face value, but if I don't, I'm not saying that you are wrong, I'm only saying that I am not sure that you are right and I would like further input to allow me to reach that state of grace.".


In reply to Re: How do I know what I 'know' is right? by liz
in thread How do I know what I 'know' is right? by BrowserUk

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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, 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
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others chanting in the Monastery: (7)
    As of 2018-06-22 17:28 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (124 votes). Check out past polls.