Procedure:

1. Find a process your company has that is inefficient.
2. Whip up a solution in under 40 hours that saves the company significant resources by streamlining the process.
3. Do #2 in your spare time.
4. Demo the solution to upper management, emphasizing the cost/benefit ratio as well as the time-to-market.
5. Be prepared to be called a liar.
6. Have a bodyguard for a few days to make sure you don't get jumped by the other developers in the parking lot.
7. Eventually, upper management will either see the light or you will find a better employer.

   ---

   • In general, if you think something isn't in Perl, try it out, because it usually is. :-)
   • "What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?"

   ---

   In reply to Re: use Perl; by dragonchild
   in thread use Perl; by ady

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

   ---

   • 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.