Waldo JaquithPlease, please, stop using "foo" and "bar” in code documentation. Give us real examples that mean something. Not "if (foo > bar)," but “if (height > limit)." Not “foo++” but “counter++”. Give us a logical hook to hang our hat on, not nonsense words.
PHolder 
@waldoj As some of your commenters have implied, these two "words" are variable names that are derived from a long military tradition.. from FUBAR (which I leave to your own efforts to define.) You don't like them, and yes, I agree that examples CAN be made better, but also don't denigrate them without realizing they have 5 decades or more of history behind them. Just like why i, j, k and l are frequently loop variables because of the history of implicit typing in FORTRAN. Know your history!
@PHolder As an exhausting language pedant, I am very familiar with the history. It has zero relevance to my point.
Martin Johnsson@mrtnj @waldoj You know that old saw about opinions, I'm sure.
Continuing with the history lessons I guess: We all have it lucky today where we can have very lengthy names for things. That hasn't always been the case, Microsoft BASIC 2.0, for example, allowed up to two letters for a variable name. And you wanted to keep it short anyway, because the variable names used RAM and 3.5K on a Vic-20 was very limiting. And then of course variable names in machine language are zero characters long.