Highly-paid consultants seem to get a lot of flak on this site, especially those who's number negation algorithms come with the prerequisite of installing an extra CPU fan. But certainly not all highly-paid (or, in Kent's case, highly-billed) consultants are bad; heck, Kent's job is to actually go in and make things better! Fancy that.

At a client's site a while back, one of Kent's responsibilities was to start code reviews for the developers. During one of the first reviews, he noticed a certain develop had no exception handling code. "Yah yah yah, I know," the developer explained, "I was just being lazy." A few days later, the developer returned to code review with his exception handling changes, each taking the form of this ...

try
{
  /*  ...  */
}
catch
{
  throw;
}