//你不需要理解这个

经典。

有一次，我在另一个讨论中看到这样的内容:

// I can't divide with zero, so I have to divide with something very similar
result = number / 0.00000000000001;

聪明的解决方案，不是吗?(如果有人不确定，这就是个笑话)

// StupidCompilerDontInline(SCDI), in the test project where
// allcode was in a single cpp the compiler had inlined nearly
// everything which lead to nice stackoverflow.
// To prevent this the metods are made virtual
#define SCDI virtual

几年前，我在一个没有单元测试可言的大型代码库中工作。

代码中隐藏了一个执行一些日历计算的方法。它有点坏了，由于一些不幸的情况，不得不以一种非常笨拙的方式处理夏令时。

我们不得不修了几次，每一次，我们都会在几个月后发现一些东西坏了。

在花了一整天的时间修复和分析之后，我把代码放到了源代码控制中，并附上了这样的评论:

// this code was written after a version trying to do {this} failed because of {reason},
// previously we were doing {this} which failed because of {reason}. This is 
// now written {this} way so that {lots of reasons here}. If you want to touch
// this code, please make sure that it produces the right answers when tested with:
//
// {some sort of unit test}

最终，我的团队被外包了。有时我想知道这段代码发生了什么:)

在一个名为“Bar”的类中(这是一个不具有描述性名称的UI控件)，类头文件:

/// <summary>I pity the "foo".</summary>

Remove()方法:

/// <summary>A "foo" and his money are soon parted.</summary>

更糟糕的是，业务合作伙伴从生成的文档中指出了这一点。更糟糕的是，这些可能是我们从那家伙那里得到的最接近有用文件的东西。

catch (Domain.ConcurrencyException)
{
    // somebody changed it between the time we loaded it and now.
    // weird, huh?
}