comment on

I think my name should be The Quick, The Dirty and The Ugly.

I have a boss that will be busy with something and suddenly stop and ask me to whack a script together quickly to do something for him... 7 times out of 10 I come straight to Perlmonks the other 3 times I can basterdise something I have done earlier.. (I keep everything)

The other day he wanted to test a Windows event log reader and needed to have certain events in the Event Log. A while ago I did a piece that did exactally that in a test so I could incorporate it in my Windows applications for error logging. In 30 secs I had added getop (which I had in another old test script) to the test code and "ta-da-aaa" a script that could take command line args and write them to any of the Windows event logs with the relevant Event ID's etc. etc.

Solved the bosses problem in no time. This is ONE example but there must be many ...You gotta love something that makes you look soo effecient...

-----
Of all the things I've lost in my life, its my mind I miss the most.

In reply to Re: Quick & dirty reasons to love Perl by AcidHawk
in thread Quick & dirty reasons to love Perl by greenFox

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.


Perl: the Markov chain saw
	PerlMonks