Typical Technical Jargon
Published Mar 03, 2004
In a software design meeting, we were using typical technical jargon to discuss a data exchange interface with a vendor. One co-worker said the programming we had ordered was delayed because the vendor was suffering from a "severe nonlinear waterfowl issue." Curious, the team leader raised his eyebrows and asked, "What exactly is that?"
The programmer replied, "They don't have all their ducks in a row."
Originally published March 04, 2004.
