User error: Difference between revisions - Wikipedia


Article Images

Line 2:

{{Use dmy dates|date=April 2020}}

{{Redirect|ID10T|the podcast|ID10T with Chris Hardwick}}

A '''user error''' is an error made by the human [[End-user (computer science)|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]] term 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") and, '''skill issue''' ("lack of skill"), and other similar phrases are also used as slang in technical circles with derogatory meaning.<ref name="Wired">{{cite journal

| url = https://www.wired.com/wired/archive/4.10/jargon_watch.html

| title = Jargon Watch

| date = October 1996

| journal = Wired Magazine

| volume = 4

| issue = 10

| archive-url = https://web.archive.org/web/20000823110056/http://www.wired.com/wired/archive/4.10/jargon_watch.html

| archive-date = 23 August 2000

| url-status = live

}}</ref> 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 the problems are caused instead by poor [[product design]]s that fail to anticipate the capabilities and needs of the user.

Line 23:

{{quote|For example, suppose the goal of your program is to allow people to convert digital camera photos into a web photo album. If you sit down a group of average users with your program and ask them all to complete this task, then the more usable your program is, the higher the percentage of users that will be able to successfully create a web photo album. To be scientific about it, imagine 100 real world users. They are not necessarily familiar with computers. They have many diverse talents, but some of them distinctly do not have talents in the computer area. Some of them are being distracted while they try to use your program. The phone is ringing. The baby is crying. And the cat keeps jumping on the desk and batting around the mouse.

Now, even without going through with this experiment, I can state with some confidence that some of the users will simply fail to complete the task, or will take an extraordinary amount of time doing it.<ref name="joelon">User Interface Design for Programmers&nbsp;– Chapter 6: {{cite web | url= http://joelonsoftware.com/uibook/chapters/fog0000000062.html | title = Designing for People Who Have Better Things To Do With Their Lives | first= Joel | last= Spolsky | archive-url=https://web.archive.org/web/20020207121722/http://joelonsoftware.com/uibook/chapters/fog0000000062.html | archive-date = 7 February 2002 | url-status=dead}}</ref>

}}

Experts in [[interaction design]] such as [[Alan Cooper]]<ref name="cooper">{{cite book

| first = Alan

| last = Cooper

| title = About Face: The Essentials of User Interface Design

| year = 1995

| publisher = John Wiley & Sons (Non-Returnable)

| isbn = 1-56884-322-4

| url = https://archive.org/details/aboutfaceessenti00coop

}}</ref> 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 Tognazzini|Bruce "Tog" Tognazzini]] describes an anecdote of ''[[Dilbert]]'' creator [[Scott Adams]] [[data loss|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.<ref name="asktog">{{cite web

| url = http://www.asktog.com/columns/069ScottAdamsMeltdown.html

| first = Bruce

| last = Tognazzini

| title = The Scott Adams Meltdown: Anatomy of a Disaster

| work = Ask Tog

| archive-url = https://web.archive.org/web/20060203032313/http://www.asktog.com/columns/069ScottAdamsMeltdown.html

| archive-date = 3 February 2006

| url-status = live

}}</ref>

[[Jef Raskin]] advocated designing devices in ways that prevent erroneous actions.<ref name="raskin">{{cite book

| last = Raskin

| first = Jef

| year = 2000

| title = The Humane Interface: New Directions for Designing Interactive Systems

| publisher = Addison-Wesley Professional

| isbn = 0-201-37937-6

| quote = See chapter 6-4-2

| chapter-url = https://books.google.com/books?id=D39vjmLfO3kC&pg=PA178

| chapter = Messages to the User

}}</ref>

Line 70:

== Acronyms and other names ==

<!-- Don't add unsourced definitions -->

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<ref name="uf_19980506">{{cite web |url= http://ars.userfriendly.org/cartoons/?id=19980506 |title= User Friendly Cartoon |work= [[User Friendly]] |date= 6 May 1998 |first1= J. D. |last1= Frazer |last2= Illiad |author-link= J. D. Frazer |archive-url= https://archive.today/20130804194429/http://ars.userfriendly.org/cartoons/?id=19980506&mode=classic |archive-date= 4 August 2013 |url-status= live }}</ref> 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/PEBCAK/PICNIC ===

Phrases used by the tech savvy to mean that a problem is caused entirely by the fault of the user include PEBKAC<ref name="catb_pebkac">{{cite web | url= httphttps://www.catblandley.orgnet/jargonhistory/htmlmirror/P/PEBKACjargon.html| title = The JargonNew File,Hacker's versionDictionary 4.4.7 | agency= maintained by Eric S. Raymond | publisher = catb | archive-url = https://web.archive.org/web/20130204161015/http://catb.org/jargon/html/P/PEBKAC.html | archive-date = 4 February 2013 | url-status= live}}</ref> (an [[acronym]] for "problem exists between keyboard and chair"), PEBCAK<ref>{{Cite web|date=2019-06-17|title=PEBCAK|url=https://techelper.io/pebcak/|access-date=2020-07-07|website=TecHelper|language=en-US|archive-date=7 July 2020|archive-url=https://web.archive.org/web/20200707184805/https://techelper.io/pebcak/|url-status=live}}</ref> (an alternative, but similar, acronym for "problem exists between chair and keyboard"), [[List of U.S. government and military acronyms#P|POBCAK]] (a US government/military acronym for "problem occurs between chair and keyboard"), PICNIC<ref name="bbc_6124438">{{cite web |last= Heald |first= Claire |url= http://news.bbc.co.uk/2/hi/6124438.stm |title= Let's help to herd the dinosaurs |website= BBC News |date= 7 November 2006 |archive-url= https://web.archive.org/web/20110516002425/http://news.bbc.co.uk/2/hi/6124438.stm| archive-date = 16 May 2011|url-status= live}}</ref> ("problem in chair not in computer") 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<ref name="adjab_intel">{{cite web|url= http://www.adjab.com/2006/10/26/pebcak-ads/|title= vPro "Go Pro" advertisements|publisher= Intel|agency= AdJab|date= 26 October 2006|archive-url= https://web.archive.org/web/20091108155142/http://www.adjab.com/2006/10/26/pebcak-ads|archive-date= 8 November 2009|url-status= dead|access-date= 4 September 2009}}</ref><!-- The adjab.com link says PEBCAK, but the actual Intel ads said PEBKAC. --> to promote its [[Intel vPro|vPro]] platform.

=== ID-10-T error ===

ID-Ten-T error<ref name="catb_idiot">{{cite web | url = http://www.catb.org/~esr/jargon/html/I/idiot.html | title= ID10T error | publisher= catb | archive-url = https://web.archive.org/web/20031004011038/http://catb.org/~esr/jargon/html/I/idiot.html | archive-date = 4 October 2003 | url-status= live}}</ref> (also seen as ID10T and ID107) is a masked jab at the user: when ID-Ten-T is spelled out it becomes ID10T ("[[Idiot (usage)|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.<ref name="uf_19990211">{{cite web |url= http://ars.userfriendly.org/cartoons/?id=19990211 |title=UserFriendly cartoon|work =[[User Friendly]] |date = 11 February 1999 |first1= J. D. |last1= Frazer |last2= Illiad |author-link = J. D. Frazer |archive-url = https://archive.today/20130804194650/http://ars.userfriendly.org/cartoons/?id=19990211 |archive-date = 4 August 2013 |url-status= live}}</ref>

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

Line 86:

=== In other languages ===

{{More citations needed section|date=March 2022}}

In Danish it is called a ''{{lang|da|[[:da:Fejl 40|Fejl 40]]''}}, or "Error'error 40"', indicating that the error was {{Convertconvert|40|cm|in|sigfig=2}} 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 ''{{lang|sv|skit bakom spakarna''}} ("'shit behind the levers"') or ''{{lang|sv|skit bakom styret''}} ("'shit behind the steering wheel"') or the abbreviation "{{lang|sv|SBS-problem"}} is used. A variant used in the [[Information and communications technology|ICT]] domain is ''{{lang|sv|skit bakom tangenterna''/tangentbordet}} ("'shit behind the keys/keyboard"') abbreviated "{{lang|sv|SBT"}}.

In French it is described as an "{{lang|fr|ICC"}} problem (''{{lang|fr|interface chaise-clavier''chaise–clavier}}), a problem with the keyboard-chairkeyboard–chair interface, very similarly to the PEBKAC.

In Québec it is called a ''{{lang|fr|Cas-18''}}, indicating that the error was {{Convert|18|in|cm|sigfig=2}} from the device. Better known as "Code'code-18"'.

In Brazilian Portuguese it is often called a "BIOS problem" ({{lang|pt|''Burro'b'''icho Idiota'''i'''gnorante Operando'''o'''perando o Sistema'''s'''istema}}),<ref>{{Cite web|title=Tirinha: Piadinha velha|url=https://vidadesuporte.com.br/tag/bicho-ignorante-operando-o-sistema/|access-date=April 14, 2024|website=Vida de Suporte}}</ref> translated as "Dumb'dumb Idiotanimal Operatingoperating the System"system', or a USB error ({{lang|pt|''Utilizador'u'''suário Super'''s'''uper Burro'''b'''urro}}), translated as "Super'super Dumbdumb User"user'.{{Citation needed|date=August 2018}}

In Spanish, some call it 'Error 200' ({{lang|es|error doscientos}}), because it rhymes with the explanation. When asked for the full explanation, it's often offered as "{{lang|es|sí, error 200, entre la mesa y el asiento}}" ('yeah, error 200, between the desk and the seat'). Other multiples of 100 also work because of the same rhyme. Also called "Error de capa 8" (8th layer error) referring to the OSI Protocol layers<ref>{{Cite web |title=What is the OSI Model? |url=https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/ |access-date=April 11, 2024 |website=Cloudflare}}</ref> when the user is the one who caused the error, for example "El servidor no es accesible por un error de capa 8" (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 "DAU" (''Dümmster anzunehmender User''), literally translated as "dumbest assumed user", referring to the common engineering acronym "GAU" (''Größter anzunehmender Unfall''), for a [[Design-basis event|maximum credible accident]], or [[worst-case scenario]].▼

▲In German it is called a "{{lang|de|DAU"}} (''Dümmster{{lang|de|dümmster anzunehmender User''}}), literally translated as "'dumbest assumed user"', referring to the common engineering acronym "{{lang|de|GAU"}} (''Größter{{lang|de|größter anzunehmender Unfall''}}), for a [[Designdesign-basis event|maximum credible accident]], or [[worst-case scenario]].

In Bulgarian it is called a {{lang|bg|Problem with behind-keyboard device}} ({{lang|bg|Проблем със задклавиатурното устройство}}).

===In subcultures===

Line 115 ⟶ 119:

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.<ref>{{cite web |last1=Smith |first1=Rebecca |title=What Does 'Skill Issue' Mean on TikTok and in Gaming? |url=https://www.gamerevolution.com/guides/913224-tiktok-skill-issue-meaning-gaming |website=GameRevolution |access-date=12 March 2023 |date=11 November 2022 |archive-date=31 January 2023 |archive-url=https://web.archive.org/web/20230131230134/https://www.gamerevolution.com/guides/913224-tiktok-skill-issue-meaning-gaming |url-status=live }}</ref>

== See also ==

Line 131 ⟶ 135:

{{reflist}}

[[Category:Computer humorhumour]]

[[Category:Computer jargon]]

[[Category:In-jokes]]