0530
After months of late nights, the toil is finally over.... not. Oh well. The system that my team and I had been working on had finally gone live on the 19th of May. Things were seemingly hunky-dory, but there were some critical errors that really put some serious doubt into the minds of the ends users. They were already resistant to change of operations, and thus they took the opportunity to sink the ship by complaining to the President directly (some vindictive bastard is pretty well-connected). Instead of sending my system to the depths of abandoned software, it survived by a thread. Instead of the 22 branches that it is deployed in, it is now constrained to 7 branches. I am now under public scrutiny. Well, the problems started from a bad server configuration. The database was not allocated enough space, the maintenance plans were not in place, the servers were not time-synchronized, the NLB was creating havoc with the viewstate verification and the identity we choose for the application pool somehow cause the .NET framework to crash multiple times during the day. The cumulative effect of these problems most probably cause erratic and erranous behaviour and we had a hell of a time patching the data. My General manager sat with us till 5:30am! The lot of us went for a dim sum breakfast and later went home to sleep before getting back to work again after lunch. :S. Things seem better now, but I wonder if it's because the load has been lessened. Have to continue monitoring the server logs... Sienzzz...
P.S.: This happened last week, so I have recovered. Jangan risau. :P
P.S.: This happened last week, so I have recovered. Jangan risau. :P
Comments
i think u need take a good rest la, so stress ur job. maybe time to change to a more flexible job. got plans for this?
Have not a clue what you said...yet again. Well, a least I didn't zzz when reading it...unlike you ;-)
Glad you survived.
No problem lo. Will see you some other time. Hehe. You sound like JJ.
@Cheryl:
I'd rather sleep actually!
@JJ:
Blek.