Raymond & Sifoo Wong are finally back in the office after their seemingly neverending overseas postings! Saw The Director (TD from now on) and he said that the next one to go again is myself and “the cycle begins again”. Oh, but it won’t be anytime soon… I intend to go back there as a programmer and not as a middleman between users and vendors. What can I say, I like getting my fingers deep ‘n’ dirty in code, muwahahhaa!
Anyway, I’m inspired by the tales of their recent exploits to write about my last trip to Cambodia, hehe. When I was there for 2 months, I only had to stay ’round the clock twice, which is considered really good considering the worse month-end disasters that the others encountered (not through any fault of mine!!!). One time was to do a major application housekeeping (imagine when the “ideal” storage should be 1 – 2 years worth of data and the company is storing 5-6 years worth…!) and the other time was to seal a password whose’s username is being used for connecting between applications and database. Minor kinks occurred, but it was kinda fun to solve them on the fly.
Pictures from the late night housekeeping activity:
Housekeeping is not such a straightforward task. You cannot just purge records from the database without affecting the reports, especially in the case of customer account statements. An entire new customer statement had to be designed with a new cutoff “brought forward” balance, and the script run to cut the database had to be correct in order to ensure no active transactions / deals are being deleted.
This would’ve been a whole lot of easier if this is an application that we ourselves designed. Since it’s not, it’s kinda like walking into a forest in the middle of the night armed with a pair of scissors to defend yourself. *bad analogy, but let’s ignore it*
After we cut the database (and since we are trimming so many years worth of data which runs into GB worth), the script itself takes a shitload of time. The fact that after EOD, we had to do 3 times worth of backup also took time. And after that we had to generate a SHITLOAD of reports for the users to check that after housekeeping, all is well. It sounds simple, but tedious, no? The problem is that we are given about 6 hours for the whole thing to wrap up, and there was just not enough time. When users are doing their checking, you have to be ready and on stand-by to answer any question if they said, “This doesn’t match”, or “There’s a difference between the before / after copy” or my least favorite, “I actually need report XXX as well. Can you regenerate for me?”
Believe me, this all takes time. The reports are all being printed on a slowass line printer (time to upgrade, people) and even running the reports to get the softcopy takes time. It’s just how the original reports were designed, of cos. There were a few hiccups here and there, at one point was rushing from one PC to another to transfer files, but it was all good. Anyway, it was quite fun also, in a way. You bond with people when all of you have been awake for > 24 hours. Hehehe.

After the initial backup & script running, the other two system support people dozed off, leaving me to deal with the reports and John for “ad hoc” requests. Hehhe. John is from the DB team, I’m from application support in case you haven’t figured out by now. Anyway, not being angry with the above 2, they really do help to support us a lot, just teasing. ;P

Sana checking her reports, Smey in a corner… donno doing what. Lol, another RakhSMEY was checking on GL and account statements… the fact that this SMEY can wander in to the office at about 3 – 4 am for no reason is kinda astounding.

Phiden from Trust Receipts diligent at report checking too.

Sana again… I LOVE THIS WOMAN OKAY!! She’s a wonder to work with – but I think it unfair if I only praise her and not all my other nice users as well. Hehhee. Anyway, she got promoted from Sr Officer to Asst Branch Manager already, so it just shows how capable this woman is. More about her in another entry.

Myself and John, almost crossing the finishing line ady. See how wonky my eyes are?
Why do I insist on posting haggard photos of myself to scar my own image?!

Me showing Tara & Mr Ho … something serious. Averting crisis!! Problem solving!!
See how cool & calm I look? 4 years of programming and application support to develop such a nonchalant demeanor hohoho!

Signoff to say “Yup, everything’s A-OK after the housekeeping activity!”

Pictures I took of myself before the entire activity started (during lulls, like waiting for the script to run while reports are being printed. There’s really nothing you can do in between, the other servers for testing are being used to recover the copy of the database BEFORE housekeeping, etc etc.
See them eyebags? Even BEFORE the activity started they were so hideous looking. Told you, going for overseas assignment ain’t no stroll in the park. Cos they pay you extra, they expect you to work extra too, naturally.
At the end of the day, this activity was extremely successful. I was just disappointed that the vendor didn’t show up for onsite support. Like hello, it’s YOUR application system and we had requested you to be on standby too. I shot off some rather sharply-worded emails to one of them, and he told me the next day that he was on standby… BY THE PHONE IN HIS HOTEL ROOM. So good, no? -___- And he said that if we wanted him to the bank, we should’ve send a 4WD to pick him up. Like, the rest of us WALKED there ok. DOT DOT DOT.
Pictures from the sealing SA password activity:
For the sealing of “SA” password, we didn’t have to stay back thatttt late. The main activity was ensuring that applications connecting to the database were still in order after changing the password. The reason Monica came along was because we had to call in the 1st half and 2nd half password holders to key in the password when we were doing the activity. Yup, IT division just love calling back people in the middle of the night, hehehe.
This implementation was not so smooth, but at least all kinks were ironed out by the end of the week, which is considered fa-fa-fa-bulous since once again, we are navigating a dense forest armed with pair of scissors to hack away at the undergrowth.

Mr Ho, this time alert and studying reports.

Both Randy & Sorivong on standby. Everyone who has met the both of them always asks the inevitable…. “So, who do you think is more handsome?” -___-

This time Mr Ho is more “seng mook” and provided food for our late night activity.
You can so tell that Monica just woke up and waltzed in to key her half of the password. Note hair!

The food is placed on top of recycled line A2 paper… lol. I forgot the name of this noodles, start with “Ba” something. It’s local hawker food, just kueh tiow fried in tomato sauce with TONNES of veggies and pork.

Close up on the generous portions.

Random closing picture of Phaerom, operator working the night shift.
Nothing new in my life… becoming too lazy to even step out of the house and go shopping. Think I’m old… too lazy to go anywhere. I’m rejoicing at the thought of more late night work at the office… contemplating staying at the office for about one week for this activity. Maybe it’s the petrol hike… trying to save costs on travelling to work. KIAMSIAP!!!
Btw, I freaking hate the fact that I can’t use credit card to pay for petrol at the pump anymore. Like HELLO?? That was my main reason for getting a cc in the first place. Bloody hell, only in Malaysia do they enjoy making life more difficult. If you complain, people say things like, “You should cut back on spending, the little bit more of walking never hurt anyone, you should blablabla” which always results in some sort of sacrifice on OUR OWN PART.
Because you know, everyone knows that you work hard to get more money in life in order to do things the DIFFICULT WAY and to give the money back to the _________. To improve things that never improve. Ok, beating a dead horse here, but I had to take the KTM the other day, and I was thinking, after THREE years of not taking KTM, MAYBE MAYBE things have improved, but of course they haven’t. I think the main problem with the KTM… (and herein I think is where I should be awarded with a Nobel Prize) is that people do not know where the train is going to stop. Think about it — for LRT, they marked where the train doors are going to open, so people can line up and there’s some semblance of order (even if you have to mark out with ropes and red lines on where & how to line up…
But yeah, the KTM has no such system. People randomly just CROWD at the station, and if you are unlucky enough (read : like me), then even though you are one of the earliest mofos there, you won’t be able to board the train when it comes. Honestly, do you carry NOTHING on the train? Not even a handbag? Not even a briefcase?? I have seen WITH MY OWN BEADY LITTLE EYES two attempted pickpockets (and in my own screwed up manner managed to “stop” them, hehee) and I really do not feel safe squashing in with the sea of people. I rather wait the, oh what’s that… oh FORTY MINUTES for the next train to arrive.
In conclusion, if they find a way for the KTM to stop at designated points so that the passengers can queue up properly to board the train, expect to see an instant 50% less complaints, fo shizzy. HAHAHHAA. Such an obvious solution, why no one talk about it before ar? Is it because it’s physically impossible for the train to do so?
Recent Comments