try {
  dataSource.close();
}
catch (SQLException ex) {
  // Do nothing, since we're going to trash this anyway
}

当然，这类事情实际上是JDBC(或者至少是Oracle的JDBC驱动程序)中的wtf，因为它可以在关闭连接时抛出SQLExceptions…

Repeat
    ...
Until (JesusChristsReturn) ' Not sure

在一个著名的商业DOS电子表格应用程序中:

/* This comment was just added in order to check-in a file that was last 
checked in by [Insert Programmer FirstName] "Back-to-the-Future" [Insert 
Programmer LastName]. While testing for year 2000 problems, he accidentally 
checked-in this file while his machine clock was set forward to the year 2000. 
This meant that the source code was always newer than the object file and 
compiled every time the code was built. I'm checking this file in again to 
fix that. */

我告诉学员至少做一些异常处理。这是我在每一个db调用....返回

Catch (Exception e) {
    //eat it
}

我参与的一个大型项目在自动构建中使用了StyleCop和FXCop，并使用规则来防止人们检入带有未注释字段、方法、属性等的代码。

有些人对必须添加“获取或设置全名”之类的注释到自记录属性(如FullName)感到非常恼火，以至于他们不得不努力编写一个宏来绕过这些规则。

宏为方法、属性等插入了XML摘要标记，其中一个单一的不显示Unicode字符作为标记内容，这将欺骗构建规则，同时对为了注释而盲目坚持的东西进行轻微打击……

.．.至少直到他们引入了另一条规则来检查注释中的Unicode字符。

catch (Domain.ConcurrencyException)
{
    // somebody changed it between the time we loaded it and now.
    // weird, huh?
}