Hacía años que no me reía tanto. Hasta las lágrimas  se me salieron.

Resulta que en computación desde el punto de vista de desarrollo, se habla de low endian, big endian que tiene que ver con la forma en que se manejan los enteros (principalmente) en la memoria de la computadira  y velocidad de lo mismo. http://es.wikipedia.org/wiki/Endianness este es un concepto que un programador decente que usó Delphi por años debe tener presente.

Pues buscando otra cosa fui a dar al sitio dailywtf.com especificamente : http://thedailywtf.com/Articles/The-Secret-Squirrel-Club,-a-Gun,-and-More.aspx

Copio el código. que barbaros

“I was recently tasked to fix some 508 compliance issues in a C#, ASP.NET application at the company I work for,” writes Dan Johnson, “I was warned that the code may be a little, let’s say, not well matured. That’s fine, I’ve seen bad. Architecture, style and good practices problems all aside, I began to see comments throughout the code like this:”

//don't do this -- too slow when there are many rows in the grid
//return;
//update:  actually it's pretty fast now - use it if desired and 
//don't rebuild the grid on the client because using setTargetURL DOES NOT WORK
//go ahead and do it - we're not using links for the app names now

 

“The frightening thing is that I’m not sure if there was more than a single developer on this project or not. At the time it was originally built and maintained, our department operated on a one-person-per-project rule.”

“I was working on Java/Delphi code and I could not believe my eyes when I found this comment,” writes Vladamir P.

    /** java uses BigIndian, Delphi uses little indian, while the
      two co-exist, need to convert back and forth when reading
      data in. */

“At first, I thought that maybe it was an isolated typo, that is until I looked further into the code…”

  /** convert from big indian to little indian: Remove when not using
      legacy databases or Delphi code.*/

    private final boolean doIndianConversion()