I think it's a little silly to expect someone to be productive with any tool..
It's a bit like expecting someone to sanely go and dig a road trench with a small flat sponge fish.
Not only does it not work, you look silly.
Half of a task should be analysing a problem to work out what tools are the best ones for the job.
Thankfully, where I am working, they leave me and my colleagues to work out what the best tools are, and try and come up with the best solutions we can.
Sometimes, the problems themselves are hideously boring and mundane, but looking at clever ways to achieve the ends can be quite amusing. Often, it leads me down paths of learning new things I'd never even heard of, let alone considered.
If your company is a little more.. Entrenched in it's ideals, the way to get what you want, is to look a little beyond the problem you're given, and try and find something that would work better and faster for the job in hand, and then present this info with your rationale.
It would take a silly company to turn down the work you've alreay put your own personal time into, to show how using a different tool for a particular job would save both time and money for the company, and perhaps increase reliability and maintainability to boot.
This being said, take care to make sure that you are giving an objective report. Just making a case for something you'd prefer to do, just because you like the idea more can seriously backfire if you're not actually correct.

Just a thought. :)

Malk.

In reply to RE: Productivity with iany/i tool? by Malkavian
in thread Productivity with <i>any</i> tool? by mothra

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.