有朋友經常罵我為何不把我在e-Zone及信報所寫的文放上來，為免繼續被咀咒，我今後會陸續將我的一些舊文在這裡和大家分享分享，獻醜獻醜。
第一份是我的正職，我是某大網絡廣告公司的傳訊策劃總監，我靠這
有早知？
廣東俗諺有句是「有早知，無乞兒」，看似理所當然，其實想深一層，除非是極簡單的情況，否則這句說話的對錯是無從判斷的。
假如你說：「早知今天股市會升得這麼高，我昨天便不會把股票賣了，現在還不賺個盆滿缽滿？」
假如你說：「早知今天股市會升得這麼高，我昨天便不會把股票賣了，現在還不賺個盆滿缽滿？」
Why your program should have an actual configuration file
Every so often, someone says something like 'you know, our program has aconfiguration file but also supports runtime reconfiguration via somemagic. Clearly this is wrong, so what we should do is get rid of ourconfiguration file and just make sure the running state is persistent'.If they're feeling nice, they add that the running state will be savedas an XML file.
Every time people say this, sysadmins cry. Here is a very importantthing for real deployments of your program in real environments
長但幼 or 粗但短
宜家俾兩個選擇你，二選一：
1. 長但幼
2. 粗但短
唔好問有冇第三個選擇，冇呀﹗
世上邊有咁多又長又粗嘅啫？我夠想要啦。
其實，我真係試過唔少ga。
又長又粗嘅，令人好回味好回味。
可惜，我只係遇上過一次。
長嘅，睇起
1. 長但幼
2. 粗但短
唔好問有冇第三個選擇，冇呀﹗
世上邊有咁多又長又粗嘅啫？我夠想要啦。
其實，我真係試過唔少ga。
又長又粗嘅，令人好回味好回味。
可惜，我只係遇上過一次。
長嘅，睇起
A thought on deliberately slow disaster recovery
Given my earlier entry , here is athesis: some disasters are big enough that you should stop trying torecover rapidly .
The problem with attempting rapid disaster recovery is that significantdisasters are high stress, high pressure situations. Unless you have very good checklists , this is exactly the sort ofsituation where it's easy to have something go catastrophically wrongthrough various situations; missed steps, miscommunication betweenpeople about who was doing what, failing to notice problem indicatorsunder the pressure of driving full speed ahead, interruptions and
May I have your number?
May I have your number? 這就是朋友和陌生人的分別。地球上有幾十億人，好像香港這麼細小的地方，走一趟旺角，就算是地膽你也可以不停遇見陌生人，所謂朋友，永遠都是一個小圈子，因為我們需要朋友，卻需要更多的陌生人。
對呢，
對呢，
模倣犯
改編自宮部美幸的經典小說，森田芳光導演的這齣探案電影本來是好看的，據說未讀過原著的觀眾是會覺得好的，讀過小說的觀眾卻可能會很失望。 宮部美幸的小說我讀過多部，但兩巨冊的《模倣犯》實在太長篇，我一直不敢碰