I was doing a database in Access, very simple thing - at least it was supposed to be at the start or I would have done it in Delphi. The client wanted to be able to get the customer info out of the database but they would not enter enough information to reliably identify the customer. I told them to use the phone number as the key as each customer (the way they worked, not for everyone) would have a different number. After a few frantic calls from them, (It's not working we can't enter the customer) I discovered that they were too lazy to look up the phone numbers from their old system and were trying to enter all the numbers they did not know as "n/a". In trying to sort this out for them I ended up with a lot of checking loops in the code and had the comment beside one outcome "This should never be reached if they do what they are supposed to do!!!!!!!!!"

他们还曾经问过我:“即使我们输入了错误的地址，我们如何才能找到正确的客户?”而这一切都是为了花生。

我们有一个文件，在它的一半，一个程序员试图弄清楚混乱的意义，设法将所有无意义的代码移到底部，并留下了这样的评论:

I have no idea what this stuff does below here.

另一名程序员留下了一系列嵌套的命名空间，这些命名空间的作用类似于“方向手册”，这样您就可以钻取想法中的名称空间并选择您的操作。

我没有亲身经历过这种情况，但这是一个很好的故事(详见我的评论中的解释):

#define MSGTAG_B33R     0x723 /* RIPLVB */

我曾经见过这个:

//this used to be a comment

//说明:!!待办事项

// drunk, fix later

真希望我是在开玩笑。根据编写代码的开发人员的了解，我认为他是认真的。