我曾经使用MS SQL Server Developer 2000实现了一些文档工作流(人工工作流的东西)。

它由一堆触发器组成，这些触发器将被添加到数据库中，使其遵循工作流规则。

在其中一个触发器中，微软的某个人写了如下内容:

//Determine if the database has been "Grizzlified"

(该产品的内部名称是“Grizzly”，所以我觉得这很有趣)。

$dnstime = time() + 60 * 60 * 24 * 7 * 2; //how long are you staying for vacation on mars? twooo weeeeeks. give dees people air

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

/* This is O(scary), but seems quick enough in practice. */ 

后面是四个嵌套的for循环

 * ...and don't just declare it volatile and think you've solved
 * the problem. You young punks think you know what volatile
 * means... why in my day we had to cast it volatile uphill
 * both ways, and the code still didn't work! Whippersnappers...

来自usenet的经典:

Teradyne硬件建模器代码的深层是一个例程 一大堆十六进制数字到SYS$QIO调用中。唯一的评论是 “这里发生了奇怪的魔法”。