Now, although I've managed to get rid of the majority bugs in the program, all of a sudden there will be some other bugs, carefully hidden, camouflaged in sequence of codes, ready to jump out on me and cause me aneurism the whole afternoon. It's been this way since Monday, as I've updated the code but the new codes just simply contain too many bugs and junks. Well, you know typical Micro$oft code, when you patch your program to fix the old bugs, new bugs will somehow appear.

My localization officer is scratching his head now as how all these bugs appeared. I've already told him not to grandeur a particular project, for the management drones love nothing but to take it to the next step and market it to everyone as their own handiwork. Even they place the correct credit, they'd still be the one known for initiating the project. And when the shit hits the fan, they'll run for cover, and push us programmer onto the incoming crap.

I told him I can write a better code if he have shifted to a better programmer (*ehem* yours truly *ehem*). However, they believe a Mat Salleh (a Caucasian) can write a better code rather than a Chinese guy who spend his holiday writing assembly codes. Of course luckily I don't have to deal in assembly as it's already been too long since I've touched the subject. I’m getting rusty in assembly so I rather not delve into that.

So, I’ve managed to complete most of the basic elements of database functions, such as listing, reading, writing & updating but many others like advanced search & multi interface logon coding still need a lot of time to be figured out. Getting too sleepy for using my brain above 4%, so I’m practically slumping when the localization officer still asked me to do additional stuff...