在20世纪80年代早期的某个时候，我们在PL/I中为公用事业编写财务建模代码。接到一个客户的电话，说代码在评论之后就爆炸了

/* Honest this works */

这家伙用了我们的标准金融方程花了大约15页的代数把一堆代码组合成一个方程。在三里岛事件后，当公用事业公司不得不以巨大的代价注销他们的核电站时，这个方程失败了，因为FIXED BIN 15(整数)溢出，如果代数没有发生，就不会发生这种溢出。

不是代码注释，而是SVN在同一个文件上提交注释:

第一次提交(在测试人员返回结果后，再进行数十次提交):

Squashed some IPR mod bugs. The were big and juicy ones, too.

2日提交:

Squashed some more mod bugs. Those are some nasty bugs, them mod bugs...

3rd:

Squashed some more mod bugs. They are like cockroaches: they'll live through a nuclear war.

4th:

Squashed some more John bugs. They too are like cockroaches: they appear anywhere John goes. Wait. That doesn't sound right.

5:

Same John bug. It didn't die, just played 'possum.

是的，我厌倦了"修复bug"

/*这是一个可怕的黑客攻击的副本——很多年前，遗留的PortfolioServer被修改为在“optionTrade”块中返回现金交易，因为客户端开发人员太懒了，没有正确地获取他们的xpath。他们的懒惰一直在回响，这意味着我们在这里需要一个类似的黑客……*/

[onload_1;block=begin;when 1=0]

Some of the techinques in this template are rather obscure, just trust me, they need to be there.
OTOH a better sollution would be to create a few seperate templates and pick one in the php-script...

[onload_1;block=end]

/* Please work */

不是注释，而是属性

[ThereBeDragons]

还有一个是我在IHttpHandler的实现中看到的

//What is this?
public bool IsReusable
{
    get{return false;}
}