我们有一个小组项目，使用最小-最大树创建一个Connect 4 AI。在我们的move-scoring函数中，我们让它为棋盘计算分数，在这段代码之上有这样的注释:

// This is kind of almost useless

但还有更好的。我们的导师给了我们一些他制作的粗糙AI的示例代码，并留下了很好的评论:

// We also add/subtract some points based on what's going on, on the bottom
// row. (I think this is retarded, but apparently when I coded this up 
// back in 1999 I didn't.)

看这个:

'On Error Goto Hell.

// This code was written by a genius so don't try to understand it with
// your tiny little brain.

我不止一次使用过这个方法，当我对一个数学公式做了一些不明显的简化时，我不想记录:

//this formula is right, work out the math yourself if you don't believe me

我经历了一个睡眠不足的编程过程，开始只写引用自《搏击俱乐部》的评论。

多年后，我仍然在浏览代码，发现了一条让我发笑的评论。大多数只是随机的想法。然而，我确实保持我的评论行比率相当好!

// This shouldn't happen. The only way this can happen is if the
// <code>JFileChooser</code> has returned a <code>File</code> that doesn't exist
// on the system. If this happens we can't recover, and there is more than likely
// a rip in the space time continuum that the user is too distracted by to notice
// anything else.

 /**
   * This method leverages collective synergy to drive "outside of the box"
   * thinking and formulate key objectives into a win-win game plan with a
   * quality-driven approach that focuses on empowering key players to drive-up
   * their core competencies and increase expectations with an all-around
   * initiative to drive down the bottom-line. I really wanted to work the word
   * "mandrolic" in there, but that word always makes me want to punch myself in
   * the face.
   */
private void updateFileCountLabel() {

一个奇怪而恰当的有趣错别字:

断言(0);//永远不要在这一点上犯错