从2004年的Windows泄露事件来看，

__inline BOOL
SearchOneDirectory(
                  IN  LPSTR Directory,
                  IN  LPSTR FileToFind,
                  IN  LPSTR SourceFullName,
                  IN  LPSTR SourceFilePart,
                  OUT PBOOL FoundInTree
                  )
{
    //
    // This was way too slow. Just say we didn't find the file.
    //
    *FoundInTree = FALSE;
    return(TRUE);
}

/*
* After 36 hours, 2 holes in my wall and writing my code right beside the API
* this still doesn't work.
* function getMap():void takes in an event object @param: evt:mouseEvent
* I will now retire for the day with a bottle of rum and 2 hours of crying
*/

// human madable inconvenient. Way too sucks.

我仍然没有完全理解它的含义，但我发现它对于许多代码来说是非常正确的。

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

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

Remove()方法:

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

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

//Woulda
if(x) {}
//Shoulda
else if(y) {}
//Coulda
else {}

我想我有过这样的经历:

if (case1) { // trivial
...
}
else { // we are screwed
 /* fill in later */
}

好吧，我可能用了一个比搞砸更强烈的词