"In computer programming, lint was the name originally given to a particular program that flagged some suspicious and non-portable constructs (likely to be bugs) in C language source code. The term is now applied generically to tools that flag suspicious usage in software written in any computer language. The term lint-like behavior is sometimes applied to the process of flagging suspicious language usage. Lint-like tools generally perform static analysis of source code." - Wikipedia (my bolding) - short alt on StackOverflow.
I know this joke won't make sense even to some of the developers I work with. On a few levels. Oh well...sometimes you just have to amuse yourself.
If you prefer to think in concrete terms, here's a nice list of static analysis tools like FxCop, StyleCop, ReSharper, and NDepend. I link directly to the .NET versions, but if you mosey around the page, you'll see all the tools for various languages, like JSLint, although you have to look elsewhere for CSS Lint.
Snarky: I mentioned we needed to de-lint our code. He had facilities wipe down our screens with dryer sheets.
Title: I'm glad you didn't say we needed to lint it.