Some of the same arguments about engaging with the community (Re^2: People who write perl, Perl and PERL) will carry over to attending conferences. 'Engaging with the community' is the bulk of the rationale behind attending academic conferences.

To get work to pay, think about it in business case terms: will the long term financial benefit of attending (in motivation and work-contentment terms as well as improved skill and productivity) outweigh the immediate financial cost of attending?

Sure, employers often send employees on what appear to be entirely pointless training courses (mandated customer service courses run by people who wouldn't recognise a customer if they were bitten by one, for example), but they perceive some definite benefit from this. At least there's a defined objective (improving ones customer skills in the example), where the learning objective of conferences tends to be rather more vague.

There's also the argument that attendance at a perl conference is likely to be cheaper than attendance of an MS approved MCSD course ;-)

--------------------------------------------------------------

"If there is such a phenomenon as absolute evil, it consists in treating another human being as a thing."

John Brunner, "The Shockwave Rider".


In reply to Re: Convincing your boss to let you go to Perl conferences by g0n
in thread Convincing your boss to let you go to Perl conferences by cog

Title:
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, 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:
    & &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.