I was going to post a message in the same vien as elbi earlier this morning, however I ran out of time.

What you are doing is making a good descision that can only help yourself, your company, and your customers in the long run. Why? Well, as you gain knowledge and experiance, you become more valuable as a '<whatever you are/do in your company>' to your company. You can tackle more complex problems with greater ease. (This can be a great assest to your company)

Having said that I must also add that you may be doing it for the wrong reasons. Personal gain on company time may or may not be ethical. That brings this to a philosophical debate. Does the ends justify the means? Personally, I don't know, and I'd rather not try to figure it out.

Down from my soap box, I will answer the question in its context. I have never let personal gain influence technical descisions. Opinion is another matter altogther. It is my opinion that BASH scripting for a certain project suffices, but Perl scripting for it is much better. Where a collegue of my has the opposite opinion. That is the beauty of opinions.

HTDCTMBAR (hope this doesn't confuse the matter beyond all recognition)

Kristofer

In reply to Re: Loyalty, Personal gain or Professional Integrity by krisahoch
in thread Loyalty, Personal gain or Professional Integrity by hakkr

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.