首先，在一个大对象的更新的开始:

/*General note to all who tread in the <ObjectName>() code...
 * The SetOriginals() method from the BaseEntity class should be called (and only called) right after the Get() method
 * call as seen above.  Calling the SetOriginals method elsewhere will result in bugs and all kinds of other nasty suprises.
 */

然后在大约200行逻辑之后更新对象:

//Attempt to explain this confusing mess of code:
//First time you save an actual absence this is what happens:
//0. The first save saves to the <TableName> table (among other things). (Fig. A)
//1. The <CalculationMethod> method is called next which inserts to the <OtherTableName> table. 
//(This is the table that keeps track of credits to the case.) (Fig. B)
//2. So then you have to call <UpdateCalculations> to move the <TableName> records to the <ThirdTableName> table. (Fig. C)
//3. Then you go back and run calculations since you have the debits table (<ThirdTableName>) populated. (Fig D.)
//4. Then a final save to save the calculations back to the case. (Fig. E)
//Yeah, I know what you're thinking:  this sucks. 10/01/07 XXX

开发商是对的……这太糟糕了!

// GK Experimental

(GK是编码器的首字母缩写)

用来表示部分代码，实际上，是实验性的。：）

这是一个很好的标志，当你在调试过程中碰到它时，你可能会在接下来的几个小时里忙着修复黑客。；）

我刚刚完成了一个日志框架(使用Trace，为什么没有这样的存在我不知道)。我做了一个继承自TraceListener的方便基类。它覆盖了所有的TraceListener方法，并将它们路由到一个方法中——因此有很多文档注释:

// TODO: Need some codemonkey to doc comment this class.

当我在高中上计算机课的时候，我们在一个普通的教室里上课——没有电脑。我们所有的测试都是在纸上完成的，一张纸上有一节课。我们的老师是第一次用c++授课，偶尔会在黑板上切换到Pascal模式。这很尴尬，因为我们中很少有人对学习帕斯卡感兴趣。

对于比课堂作业更大的作业，我们会在家里做，并提交代码和输出打印结果来评分。在提交了一些代码+输出输出后，我们共同意识到老师实际上并没有阅读代码-只是打印输出。为了测试我们的理论，我在代码的第三页放了一条注释——就在一些类声明之间:

// If you are reading this, please place a checkmark here [  ]

当然，我把它拿回来的时候，前面有一个大大的蓝色“a”，没有任何标记。

var arbitraryNumber = 10;
//I don't know why. Just move on.

我的精选集:

// Thats the end of the While loop
// Clean up last row.  I really must program better than this.

// Note: You can't immediately tell if the line below works.

// Rounding - blech.  It's assumed that all .5s are rounded up.

// Sort out predictions first.  Seems like the right place for a prediction, 'first'.

// Let's interpret!