// TODO: Drive an ashen stake through the foul heart of this function.

这是一个糟糕的函数。直到今天我还在做噩梦。

当我读到这篇关于我负责维护的项目的文章时，我哭了。

//Write Code Here

我仍然畏缩:)

有一次，我问一个同事如何用我们的内部框架做一些事情(忘了具体是什么，一些晦涩的技术调用)。 他说“简单，看这里”，然后在他的编辑器中打开一个。java文件，在几页代码中间给我看了这个注释:

// HERE

我刚刚检查了一下，注释仍然在这个文件中:)

对于我编写的memcache包装器/处理程序接口模式类，我实现了以下方法。

/**
*  Do not use, ever - left in place for testing purposes
*/
function  I_David_WillHuntYouDownAndHurtYou_Badly_IfIFindThisUsedAnyWhereInTheAppLibrary(){
...
}

这基本上是一个超级核函数，它告诉所有单独的memcache服务完全刷新自己，并从我用于键的单个名称空间计数器(例如{_counter_key value}_)重新开始。{_counter_key value})

Another minor novella I wrote was for an automated downloader for a data vendor, detailing how much I hated this vendor and went to great lengths of postulating that their infrastructure's batch system was run by a gerbil, running on a wheel and after so many revolutions of the wheel the next queued task would be started. It was written over the course of 6 months of adding additional exception handling, estoric checks like ( if we got 768 Bytes of \s characters, that means the query to their DB timed out and the spaces are the result of empty failure print statements.

大概30页的xslt的中间部分

<!-- Here be dragons  -->

最近在我们的代码中发现了这一点(我们开发企业软件):

// Instance of excel
Excel excel = this.CreateExcelInstance();
excel.Open(stream); // how to close it?!

在此之前，我确信我们已经摆脱了这些“有趣的东西”，我们正在以正确的、意识形态正确的方式做这件事……