是巧合? 还是。。。
近期，心就好像旋在半空中。
期待后，带来了失望。
有点不知所措。
就连梦境都会玩弄我：一个晚上，梦到躺在怀里，是多么的温馨，幸福的。
隔个晚上，却放了个炸弹，说自己不是单身。=.=
朋友说，我怎么老是喜欢上有主的花。
老实说，我也不知道耶。
也太巧了吧。
脑袋一直告诉自己，不要走向以前所走的路，不要再犯同样的错误！
心里却觉得，喜欢就去追，没什么不对呀！
矛盾。超矛盾的！
同事所传来的“讯息”，加入了一句“Keeping my options open”，顿时让我陷入困境。
该跟着直觉吗？或聆听脑袋的理智选择？
有一次也会告诉自己：就是朋友，不要作出太明显，太友善的举动。
这个吗，在短短的几个小时内就破功了。
也就在这时，在手机里，瞄到了看似男友的照片。
心变冷了。
说真的，我是想很幼稚的追，就算伤的自己，也只需要时间来让伤口愈合。
同事也说过，难道你就一定要等个没有主的花吗？要等到几时呀？
是否该拿出“九把刀精神”，要热血，幼稚，不按底出牌？
我想。真的，真的想。
但，我毕竟是被伤过的。疤痕就像是一种提醒：这有可能是冒险所付出的代价。
这个疤痕，就是阻止我向前的原因。
但，这个代价值得吗？
又再次体会到“世界上最遥远的距离，不是 生与死. 而是 我就站在你面前 你却不知道我爱你”，这句话的意思。
或许我应该给自己一个期限。
这段期限内，也不要太刻意。但在这期限内，必须得到一个明确的答案。
就这样吧！这是我和自己的约定！
=============================================
你，在看吗？
10/12/2011. Lunar Eclipse.
在那一刻，希望未来遇见的你，也是看着这一幕的。
=============================================
1 Jan, 2011
If there's dust on my blog, I guess it would be under 10 foot of dust! XD
Ok, let's see what happened in 2010:
- Not exactly a good year, work-wise. Got pissed by the faggot manager and the faggot Systems Engineer
- Caught up with friends whom I did not see for a long time
- Went to Hong Kong. A trip that is ranked at the bottom of my travel-experience list.
- Quit my job
- Screwed the manager and engineer big-time
- Got a new job with a better environment
- Went to Krabi again!
On the material side:
- Got my Nexus One
- Bought a 35mm F1.8 lens
- Went on 2 overseas holidays
- Changed my up-lorry speakers
- Upgraded my camera to a Nikon D7000
- PC got upgraded with new CPU, motherboard (by accident. =P)
Now, let's see what DID NOT happen in 2010:
- Nope, no Mt Kinabalu climb (due to work change)
- Definitely not attached (haha!)
Let's see what I WANT TO DO in 2011:
- Time to invest in myself: self-study and get a few more certs
- Save up more
- Travel! (Bangkok in July, Taiwan in December) <- this really contradicts the one above
And of cos, there's something that I would like to do, but it really depends alot on the timing and situation. Shall see about that.
=============================================
The most bombastic email ever in my working life
Sent out the below email to my team. This has to be the most bombastic email I have ever sent out during my 2yr + of working life! Obviously this was aimed at one person XD If an Assistant Systems Engineer (aka ME) can do all these simple stuff correctly, I don't see the reason why a Systems Engineer can get it wrong! And 5x wrong somemore!
Hi All,
Just would like to share with you on some issues I had experienced.
As some of you might know, there are occasions whereby engineers are required to do some hardware add-on (i.e. RAM, processor, PCI-e Cards) for new servers (i.e. No Operating Systems). Upon hardware add-on, engineers might not power on the server and just return the servers back to store, as the jobsheet does not indicate “DOA Check”.
There have been a few instances whereby in-house hardware add-on has been done by engineers, and when servers have been sent onsite, racked and powered on, amber light was detected on the servers. I myself experienced amber light for all 5 servers that I have racked with Arun for Sony today.
The amber light warning includes the following:
1. All 5 servers having RAM placed in the wrong slots
2. 3 out of 5 servers having processor issue
3. 2 out of 5 servers having Processor Power Modules (PPMs) issues
In this case, customer was curious on why both Arun and I have to open up the servers and troubleshoot, and explanations had to made to customer on this. Diagnostic tests and logs were also requested from customer as customer was worried that the problem might surface in the future. As Sony is one of our key accounts, I had to go the extra mile by running the tests, so as to both ensure that the servers have no issues, and that the customer have confidence in the servers.
My observation is that all the above problems could have been noticed by the performing a simple power-on test on the servers, when the hardware add-on was done in the staging room. In this case, the HP servers have indicators in front of the server, indicating PSU, RAM, PPMs, that engineers could clearly see, even without plugging in monitors & keyboard/mouse.
Once amber light has been detected, engineers could then proceed to troubleshoot the problem. In this case, the following was done:
1. RAMs were placed in the correct slots
2. As servers are dual-core servers, processors were swapped, and problem was rectified
3. PPMs, which are in pairs, were also swapped, and problem was rectified
Fortunately, the above problems could be solved by swapping the components around. If a support case has to be logged to the respective vendor (in this case, HP), customers could be faced with delays, and they might miss their deadlines.
There have been a few instances whereby I myself did some in-house hardware add-on, and was faced with amber light upon power on. Problem was rectified before servers were packed in these cases.
I had a few email exchanges with Mr Terence, and he has endorsed my suggestion that for future hardware add-on jobs, engineers perform a simple power-on test prior to packing the servers and sending them back to store. This would not take up much time, and this would save engineers and customer both time and trouble when the servers are onsite.
What does this show?
NEVER LET STEP ON MR CHOO'S TAIL. OR BEAR THE CONSEQUENCES! XD XD
=============================================
