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。
又長又粗嘅,令人好回味好回味。
可惜,我只係遇上過一次。
長嘅,睇起

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?
對呢,
模倣犯
The problem with blog footnotes
Here is something that has just occurred to me (courtesy of seeing anexample of it): footnotes are hard to do well in blogs, and may needactual software support if you want them to be completely correct.
The conventional way of doing footnotes in HTML is to use fragment URLsand anchors, with the footnote text at the bottom of the entry andyour choice of footnote markers in the main text. But, like anythinginvolving anchors, this means that you need to come up with uniqueanchor names.