May 14, 2010
New Programming Jargon
Categorization is hard. Categorization of code is boring. This list (made up of responses to a question posted on Stack Overflow) spices it up a bit by giving you FUN ways to talk about your most dreaded bugs, design patterns, and lack of documentation. A few of my favorites:
- Banana Banana Banana: Placeholder text indicating that documentation is in progress or yet to be completed. Mostly used because FxCop complains when a public function lacks documentation.
- Bugfoot: A bug that isn’t reproducible and has been sighted by only one person.
- Counterbug: A defensive move useful for code reviews. If someone reviewing your code presents you with a bug that’s your fault, you counter with a counterbug: a bug caused by the reviewer.
- Shrug Report: A bug report with no error message or “how to reproduce” steps and only a vague description of the problem. Usually contains the phrase “doesn’t work.”
- Smug Report: A bug report submitted by a user who thinks he knows a lot more about the system’s design than he really does. Filled with irrelevant technical details and one or more suggestions (always wrong) about what he thinks is causing the problem and how we should fix it.
