The past few days have me heavily desiring to have that magical wand as advertised on the Disney Channel and wave either my client or his reported problem gone. For good. But too bad for me, fantasy and freelancing don’t cross paths so I was left with no other choice but to get my hands dirty and fix the problem he’s reporting.
But the problem is that I don’t think the problem he’s raising is actually a problem. Well, at least that’s the case for me and the 3 other people whom I asked to try and test the feature that the client is reporting to be faulty.
So how do I fix a non-existent problem? A product ‘error’ that I am almost sure is caused by his own ignorance. An ID-Ten-T-Error as they call it. Below are some points that I learned from this experience.
ID-Ten-T Error (also seen as ID10T and ID107) is a term often used by tech support operators and computer experts to describe a problem that is due to the user’s ignorance instead of a software or hardware malfunction. It is a masked jab at the user: when ID-Ten-T is spelled out it becomes ID10T, l33tspeak for “idiot”. (Though the usage actually predates L33T as a part of geek culture.) It is also known as a “Ten-T error” or “ID:10T error”. (from Wikipedia)
