Teh H4x0r

Main Entry: Teh H4x0r
Phoenetic Pronunciation: \tay hack-sore\
Function: noun
Date: Late 20th century

1. an elite computer programmer, technician, engineer, or systems architect.
2. anyone who can bend a computer to their will.
3. me, muthafucka!

<--------------------->

I've been banging out so much code over the last week. My job entails much more than just programming, but I've been finding all sorts of ways to solve problems with my code-skillz lately.

On any given day I could be called upon to perform Oracle database administrative tasks, develop .NET code for web apps or services, troubleshoot client side problems, advise on third party solution architecture, or manage and coordinate project teams and activities. Oh yeah - I forgot I also do both end-user and technician level training classes. I've probably forgotten a task or two...

All of this and I serve on a rotating weekly on-call schedule with three other guys. On-call is 24/7/365 between the four of us. Hospitals never sleep, you know. Oh yeah... haha. I also develop the training material for the classes I give as well as develop the documentation for all of the systems I develop and/or support.

Anyways - back to the code. Over the last week or so I have been a veritable Indian sweatshop of code output. In this short period of time I have:

1. Added a historical record revision tracking system to our web based Change Control system (which I wrote originally)
2. Created a record reconciliation routine with excel spreadsheet output and configurable parameters to compare items sent and items received between two different systems here at the Hospital.
3. Detected, isolated, coded a fix for, tested, and deployed said fix for an issue with an Oracle monitoring service (that I wrote originally) whose output had come under criticism. In all honesty, it was a bug in my software but it was a bug that only manifested itself when a certain other group did something they should never do to my precious server.
4. Overcame our LAN group's excessively restrictive security policies in order to coordinate a vendor installation of software on a load balanced server arrangement. ("That didn't work?" Hmmm... troubleshoot, test, troubleshoot, test. Call LAN group "Hey, open up permissions on such and such registry key.")

All that and I fielded a few HelpDesk tickets, too. I'm on call this week.

Teh. Fucking. H4x0r.