In most programs I use descriptive variables that make the code easier to debug and document.

The only exception to this is the project from hell. Some idiot in the marketing department decided to sell a product that hasn't been built in ten years.

They also wanted some changes in the software and the hardware. This is a piece of test equipment that has C and assembly code embedded into the EPROM's on several PC boards. There was nobody left at the company that knew anything about the product. The software wasn't documented at all and some of the source code was missing but we still had the object files. The hardware department also had a difficult time because the schematics didn't match the PC boards.

Everybody that had to work on this project thought it was a waste of time and money except upper management.

When the C code was compiled there was about two hundred warnings. I did locate some people that originally worked on the software and they said the warnings are normal and just ignore them. We found a lot of if statements like this:  if (x=b){do_something;}. There should be two equal signs in the if statement.

For the new changes to the program we started using variables like:
waste_of_time
time_waster
money_waster
crap
worthless
piece_of_shit
junk