/*
    FIXME:  why the fuck did anyone ever think this kind of expensive iteration
                    was a good idea?

回到《Hitchhiker’s Guide》刚问世的时候，我曾经测试过某些内容是否可滚动，以及用户是否尝试着滚动，这是一种限制可变长度的语言。所以:

if (scroll and noScroll) # or tea and no tea

对于我编写的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.

try {

} finally { // should never happen 

}

我记不清了，大概是这样的:

Person p = new Person("John", "Doe", "male");
Collection women = new ArrayList();
women.insert(p.getTail());

这是肮脏的代码;)

catch (Exception ex)
{ 
    // just die already.
}