|more useful options|
Just thought I'd share my experience on how perl saved my butt as well as many long problem hours logging calls
Since Sunday evening 10pm till Tuesday afternoon 1pm no calls were logged into the HelpDesk system from the automated call logging management system. In total around 300 calls. On Tuesday afternoon all hell broke loose when management wanted to know why no calls were being logged. After about 30 mins we had sorted out the problem. Management then came up with this beaut.. "We want all calls that were missed logged." What did we need to do to achieve this? Extract all the records that did not have a corresponding call number associated with it, and then log all these calls manually. Each call would takes on average 5 mins to log, not including the time to extract the detail on the missed calls.
297 calls = 24.75hrs.. and they wanted it WHEN..?
Wannabe perl hacker, AcidHawk, has a flash of brilliance. (I take some battering at the office because I can only write in perl.) And did perl just fit for this job. 15 mins to build a script to extract the relevant records from the management system database(MSSQL). 30 seconds to run it and have a csv file output. 5 mins to build a script to reformat all the records in the csv file (all of which is 9 lines), into messages that could be replayed in the management system. Maybe 20sec to replay all messages. Time to have all calls automatically logged in Helpdesk system. 1.5 hrs.
All this was completed before the requested change control was authorised for us to start capturing the calls manually.
This has got to be one of the strengths of perl. The amazingly short time it takes to build something that works. This fact alone has made me extremely fond of perl. In fact some of the folk that give me a difficult time because I can only code in perl have now asked that I quickly “whack something together” that will update all these calls with the reason they were logged late.-----
Of all the things I've lost in my life, its my mind I miss the most.