User error

From Wikipedia, the free encyclopedia

Template:Short description Template:DMCA Lua error in package.lua at line 80: module 'Module:Hatnote list' not found. A user error is an error made by the human user of a complex system, usually a computer system, in interacting with it. Although the term is sometimes used by human–computer interaction practitioners, the more formal term human error is used in the context of human reliability.

Related terms such as PEBKAC ("problem exists between keyboard and chair"), PEBMAC ("problem exists between monitor and chair"), identity error or ID-10T/1D-10T error ("idiot error"), PICNIC ("problem in chair, not in computer"), IBM error ("idiot behind machine error"), skill issue ("lack of skill"), and other similar phrases are also used as slang in technical circles with derogatory meaning.[1] This usage implies a lack of computer savviness, asserting that problems arising when using a device are the fault of the user. Critics of the term argue that many problems are caused instead by poor product designs that fail to anticipate the capabilities and needs of the user.

The term can also be used for non-computer-related mistakes.

Causes

Joel Spolsky points out that users usually do not pay full attention to the computer system while using it. He suggests compensating for this when building usable systems, thus allowing a higher percentage of users to complete tasks without errors:

Template:Quote

Experts in interaction design such as Alan Cooper[2] believe this concept puts blame in the wrong place, the user, instead of blaming the error-inducing design and its failure to take into account human limitations. Bruce "Tog" Tognazzini describes an anecdote of Dilbert creator Scott Adams losing a significant amount of work of comment moderation at his blog due to a poorly constructed application that conveyed a wrong mental model, even though the user took explicit care to preserve the data.[3]

Jef Raskin advocated designing devices in ways that prevent erroneous actions.[4]

Don Norman suggests changing the common technical attitude towards user error: Template:Quote

Acronyms and other names

Terms like PEBMAC/PEBCAK or an ID10T error are often used by tech support operators and computer experts to describe a user error as a problem that is attributed to the user's ignorance instead of a software or hardware malfunction. These phrases are used as a humorous[5] way to describe user errors. A highly popularized example of this is a user mistaking their CD-ROM tray for a cup holder, or a user looking for the "any key". However, any variety of stupidity or ignorance-induced problems can be described as user errors.

PEBKAC/POBCAK/PICNIC

Phrases used by the tech savvy to mean that a problem is caused entirely by the fault of the user include PEBKAC[6] (an acronym for "problem exists between keyboard and chair"), PEBCAK[7] (an alternative, but similar, acronym for "problem exists between chair and keyboard"), POBCAK (a US government/military acronym for "problem occurs between chair and keyboard"), PICNIC[8] ("problem in chair not in computer"), "cockpit error",[9] and EBKAC ("Error between keyboard and chair"). Another variant is PEBUAK (Problem Exists Between User and Keyboard).

In 2006, Intel began running a number of PEBCAK web-based advertisements[10] to promote its vPro platform.

If the same sentiment wants to be conveyed without using an acronym, the phrase "chair to keyboard interface error" is often used.

ID-10-T error

ID-Ten-T error[11] (also seen as ID10T and ID107) is a masked jab at the user: when ID-Ten-T is spelled out it becomes ID10T ("IDIOT"). It is also known as a "Ten-T error" or "ID:10T error". The User Friendly comic strip presented this usage in a cartoon on 11 February 1999.[12]

In United States Navy and Army slang, the term has a similar meaning, though it is pronounced differently:

  • The Navy pronounces ID10T as "eye dee ten tango".[13]
  • The Army instead uses the word 1D10T which it pronounces as "one delta ten tango".

In other languages

Page Module:Message box/ambox.css has no content.

In Danish, it is called a Script error: No such module "Lang"., or 'error 40', indicating that the error was 40 centimetres (16 in) from the device. Swedish has a similar expression, Felkod 60, referring to the error being 60 centimeters away from the device.

In Swedish, the phrase Script error: No such module "Lang". ('shit behind the levers') or Script error: No such module "Lang". ('shit behind the steering wheel') or the abbreviation Script error: No such module "Lang". is used. A variant used in the ICT domain is Script error: No such module "Lang". ('shit behind the keys/keyboard') abbreviated Script error: No such module "Lang"..

In French, it is described as an Script error: No such module "Lang". problem (Script error: No such module "Lang".), a problem with the keyboard–chair interface, very similarly to the PEBKAC.

In Québec, it is called a Script error: No such module "Lang"., indicating that the error was 18 inches (46 cm) from the device. Better known as 'code-18'.

In Brazilian Portuguese, it is often called a BIOS problem (Script error: No such module "Lang".),[14] translated as 'ignorant animal operating the system', or a USB error (Script error: No such module "Lang".), translated as 'super dumb user'.

In Spanish, some call it 'Error 200' (Script error: No such module "Lang".), because it rhymes with the explanation. When asked for the full explanation, it's often offered as "Script error: No such module "Lang"." ('yeah, error 200, between the desk and the seat'). Other multiples of 100 also work because of the same rhyme. Also called Script error: No such module "Lang". (8th layer error) referring to the OSI Protocol layers[15] when the user is the one who caused the error, for example Script error: No such module "Lang". (Server is not accessible due to an 8th layer error) when users can not access a server because they typed in the wrong password.

In German, it is called a Script error: No such module "Lang". (Script error: No such module "Lang".), literally translated as 'dumbest assumed user', referring to the common engineering acronym Script error: No such module "Lang". (Script error: No such module "Lang".), for a maximum credible accident, or worst-case scenario.

In Bulgarian, it is called a "Problem with behind-keyboard device" (Script error: No such module "Lang".).

In subcultures

Page Module:Message box/ambox.css has no content.

The computing jargon refers to "wetware bugs" as the user is considered part of the system, in a hardware/software/wetware layering.

The automotive repair persons' version is referring to the cause of a problem as a "faulty steering actuator", "broken linkage between the seat and the steering wheel", "loose nut between the steering wheel and the seat," or more simply, "loose nut behind the wheel." Similarly, typewriter repair people used to refer to "a loose nut behind the keyboard" or a "defective keyboard controller."

The broadcast engineering or amateur radio version is referred to as a "short between the headphones". Another term used in public safety two-way radio (i.e. police, fire, ambulance, etc.) is a "defective PTT button actuator".

Another similar term used in the United States military is "operator headspace and timing issue" or "OHT," borrowing terminology related to the operation of the M2 Browning machine gun.[16]

"(It's a) carbon based error", indicates a user problem (humans are a carbon-based life-form), as opposed to a silicon-based one.[17]

Some support technicians refer to it as "biological interface error".

The networking administrators' version is referring to the cause of a problem as a "layer 8 issue", referring to the "user" or "political" layer on top of the seven-layer OSI model of computer networking.

In video game culture, user error is sometimes referred to as a "skill issue", often as a retort to the player complaining about the game's perceived unfairness.[18]

See also

Page Module:Side box/styles.css has no content.Page Template:Sister project/styles.css has no content.

Page Template:Plainlist/styles.css has no content.
Script error: No such module "Sister project logo".
Look up PEBCAK in Wiktionary, the free dictionary.

References

Page Template:Reflist/styles.css has no content.

  1. ^ Page Module:Citation/CS1/styles.css has no content."Jargon Watch". Wired Magazine. 4 (10). October 1996. Archived from the original on 23 August 2000.
  2. ^ Page Module:Citation/CS1/styles.css has no content.Cooper, Alan (1995). About Face: The Essentials of User Interface Design. John Wiley & Sons (Non-Returnable). ISBN 1-56884-322-4.
  3. ^ Page Module:Citation/CS1/styles.css has no content.Tognazzini, Bruce. "The Scott Adams Meltdown: Anatomy of a Disaster". Ask Tog. Archived from the original on 3 February 2006.
  4. ^ Page Module:Citation/CS1/styles.css has no content.Raskin, Jef (2000). "Messages to the User". The Humane Interface: New Directions for Designing Interactive Systems. Addison-Wesley Professional. ISBN 0-201-37937-6. See chapter 6-4-2
  5. ^ Page Module:Citation/CS1/styles.css has no content.Frazer, J. D.; Illiad (6 May 1998). "User Friendly Cartoon". User Friendly.{{cite web}}: CS1 maint: deprecated archival service (link)
  6. ^ Page Module:Citation/CS1/styles.css has no content."The New Hacker's Dictionary".
  7. ^ Page Module:Citation/CS1/styles.css has no content."PEBCAK". TecHelper. 17 June 2019. Archived from the original on 7 July 2020. Retrieved 7 July 2020.
  8. ^ Page Module:Citation/CS1/styles.css has no content.Heald, Claire (7 November 2006). "Let's help to herd the dinosaurs". BBC News. Archived from the original on 16 May 2011.
  9. ^ Page Module:Citation/CS1/styles.css has no content.Zimmerman, Frederick (March–April 1984). "A Z100 on Every Desk: Clarkson College". Sextant. No. 9. pp. 8–14. Retrieved 12 February 2026.
  10. ^ Page Module:Citation/CS1/styles.css has no content."vPro "Go Pro" advertisements". Intel. AdJab. 26 October 2006. Archived from the original on 8 November 2009. Retrieved 4 September 2009.
  11. ^ Page Module:Citation/CS1/styles.css has no content."ID10T error". catb. Archived from the original on 4 October 2003.
  12. ^ Page Module:Citation/CS1/styles.css has no content.Frazer, J. D.; Illiad (11 February 1999). "UserFriendly cartoon". User Friendly.{{cite web}}: CS1 maint: deprecated archival service (link)
  13. ^ Page Module:Citation/CS1/styles.css has no content."NAVspeak Glossary". Usna.org. Archived from the original on 1 December 2010.
  14. ^ Page Module:Citation/CS1/styles.css has no content."Tirinha: Piadinha velha". Vida de Suporte. Retrieved 14 April 2024.
  15. ^ Page Module:Citation/CS1/styles.css has no content."What is the OSI Model?". Cloudflare. Retrieved 11 April 2024.
  16. ^ Page Module:Citation/CS1/styles.css has no content.Roberts, G. M. (2013). The Life & Times of an Incorrigible. PublishAmerica. p. 152. ISBN 978-1-62772-272-8.
  17. ^ Page Module:Citation/CS1/styles.css has no content."What is a Carbon-Based Error? – Definition from". Techopedia. 30 January 2012. Archived from the original on 4 April 2018. Retrieved 24 April 2018.
  18. ^ Page Module:Citation/CS1/styles.css has no content.Smith, Rebecca (11 November 2022). "What Does 'Skill Issue' Mean on TikTok and in Gaming?". GameRevolution. Archived from the original on 31 January 2023. Retrieved 12 March 2023.
Retrieved from "https://cosmopedia.co/index.php?title=User_error&oldid=1425475"