The other day King Kong called me into his office to explain a new charge number recording practice that the Shitshow is currently rolling out.
He explained that this will help the Shitshow and flunktional managers determine where charge overruns are occurring allowing them to create new targeted processes to eliminate future overruns. In theory this seems like a good idea. But of course the Shitshow’s implementation is laughable.
Despite already having a specific charge number for a specific subsystem, you are now required to add an additional 2 fields of information to the charge number. One field requires you to state what type engineer you are with a 2 letter codes. Of course this code or the description of the codes doesn’t line up with the HR provided job title or functional assignment codes so basically you just have to pick whichever code seems the closest.
The other field is a free-for-all which is defined by the program based on the suggestions by the flunktional managers. King Kong then walked me through the 6 letter codes he suggested to the program I’m currently working:
script development, script debugging, script running, test development, test execution, test debugging, test preparation, test setup, test setup trouble shooting, test review, test analysis, test report generation, test report editing, test report review
script development, script debugging, script running, test development, test execution, test debugging, test preparation, test setup, test setup trouble shooting, test review, test analysis, test report generation, test report editing, test report review
Afterwards King Kong asked if I had any questions. I responded with “Yes. Can I have a charge number to figure out what charge number I should be using?” King Kong’s face immediately turned red and he then loudly lectured me, with spit flying out of his mouth for added Kong effect, on the importance of this initiative.
Because figuring out what charge number to use is the hardest part of my job, I throw rocks.