The First Link

Kaj sent me this link: Deleting code by Ned Batchelder. It's the kind of thinking my training also enforces. The gist of it is
"If you have a chunk of code you don't need any more, there's one big reason to delete it for real rather than leaving it in a disabled state: to reduce noise and uncertainty. Some of the worst enemies a developer has are noise or uncertainty in his code, because they prevent him from working with it effectively in the future."

I'll add this link to my list of useful links, too.