我告诉学员至少做一些异常处理。这是我在每一个db调用....返回

Catch (Exception e) {
    //eat it
}

//This code sucks, you know it and I know it.  
//Move on and call me an idiot later.

/* Hammer Time! */

我不知道为什么，也不知道他在写代码时是否穿着防撕裂尼龙降落伞裤

REM Don't delete this print statement ****** will die

所讨论的流程是一些遗留代码中的服务

/* Only break the connection if it actually exists. It is important to
 * check the timeslot saved in the SOURCE of the disconnect message. */

我写了这条评论，现在我不记得为什么它很重要了…

这一点对其他人来说很有趣，但对我来说就不那么有趣了。我从一个开发人员那里继承了代码(ASP)，而他自己也继承了它。第一个程序员编写了一些很难理解的代码。第二个开发者添加了如下评论(为了保护不那么无辜的人，名字被隐藏了):

'This code was written by **************.
'I haven't a clue what it does. He hasn't a clue what it does.
'Nobody else has a clue what it does or how it does it.
'It is something to do with data but **** knows what.
'The ******* still works so please do not change this code,
'even though it is a complete pile of ****.

那我为什么不觉得有趣呢?嗯，这是一个客户内部网的ASP代码。

.．.正是那位顾客向我强调了这条评论。

:-(