RTFM

This article is about the help-request response. For the knowledge-base application, see Request Tracker. For the Poster Children album, see RTFM (album).

In ray tracing or within the context of BRL-CAD, "RTFM" may stand for "ray tracing figure of merit".

RTFM is an initialism for the direction "read the faulty manual"(in time people change faulty to fucking as no one read the faulty manual). This instruction is sometimes given in response to a question when the person being asked believes that the question could be easily answered by reading the relevant user's manual or instructions. It is also used to tell people to try to help themselves in obvious ways before seeking assistance from others. In expurgated texts, substitutions such as "read the flaming manual" or "read the friendly manual" are used (or similar variants). On other occasions, the "F" is simply ignored. The abbreviation can also be found on message boards, to mean "read the fucking (or first) message", or "read the FAQ, moron".

Since the rise of the Web, pervasive internet connectivity, and ubiquitous search, a similar type of response has involved the idea that by asking questions that could easily be answered by even the most cursory, obvious search, the user embarrasses himself by showing that the very idea of searching before asking didn't even occur to him. The most common variants of this type are GIYF ("Google is your friend") and LMGTFY ("let me google that for you"), both with a tone of patronizing helpfulness (with varying degrees of sarcasm). Often the responder will even insert a link into the reply that, when the user clicks it, will take them to a saved search query. The clear implication is that "you should know by now to do this yourself."

Many alternative expansions for "RTFM" exist (particularly expurgated ones), as do many similarly themed alternative initialisms.

Possible origins

The phrase RTFM may have first appeared in print in 1979 on the Table of Contents page of the LINPACK Users' Guide in the form: "R.T.F.M." -- Anonymous. Apocryphally, some of the authors heard it from a Tektronix salesman.

The phrase RTFM was in common use in the early 1950s by radio and radar technicians in the US Air Force. Operators frequently did not check simple faults, for example checking whether a fuse had blown or a power plug had become disconnected.

Context-sensitive factors in determining (in)appropriateness

The appropriateness or inappropriateness of an RTFM or GIYF response depends on the context and the people involved.

When asking represents shirking (ant-versus-grasshopper contexts)

In contexts where the people involved are peers in a harsh (or at least competitive) environment—one where everyone is equal, there is work to be done, and each ought to pull his own weight—it can be inappropriate to ask beginner-level questions of one's peers without having "done one's homework first". The asker shows a degree of either incompetence or rudeness, which harder-working colleagues do not wish to reward. The implicit subtext in the responder's mind is, "We all have to work hard, and to learn the hard way, in this environment. If I had to work my way up to where I am, why should I reward your laziness or ineptitude with free concierge service?" This kind of situation is analogous to that of The Ant and the Grasshopper, in which the ant's refusal to suffer the foolishness of the grasshopper is understandable. This principle can be found among peers in workplaces, schools, and some online communities. For example:

• "On the job" or "in the field". It takes a certain minimum level of competence and self-guided effort to be a programmer, and most especially a hacker-grade programmer. One cannot attain the role just by asking others to hand it to him. (This is also true of many other skills in life.) Hackers have often suggested that in some situations, "RTFM" is actually the best advice that an aspiring hacker can receive. They posit that hacking is a dynamic art that requires independence and drive on the part of the hacker, and see "RTFM" as more of a long-term advisement than it is a response to any single query.
• At school. There is a difference between someone who's trying hard, studying conscientiously, and just needs some tutoring (on one hand) and someone who idly shirked his homework and now expects his peers to give him the answers (on the other). The former deserves respect and help; the latter chooses to forfeit both.

When asking is excusable or even natural

The ant-versus-grasshopper argument only applies to the types of cases discussed earlier. It does not apply in cases where the asker's naïveté is excusable (and often may be entirely appropriate). For example, technical support staff for consumer software or devices would be fired for giving RTFM or GIYF responses, because it is their job to help novices. To expect minimum background knowledge on the part of the user is not always well-founded; there is a spectrum of appropriateness for different products or services. For example, with radiographic equipment such as a CT scanner, one would reasonably require the operator to have competence in radiological safety; but for consumer electronics, the goal (distant as it often may be) is to shield the user from having to possess any arbitrary threshold of skill. In fact, when it comes to software for general-population users, the evolving standard in usability is that software be engineered (often at great pains) to be usable without a manual at all, since users don't often actually read them, and in many contexts, perhaps should not even be expected to. For example, some of the "great pains" that engineers now go to in order to shield users from complexity "under the hood" are the "contextual help" paradigm; automation (as with engine control units, anti-lock braking systems, and traction control systems that make car operation closer to foolproof than it used to be); weak artificial intelligence (AI) (such as today's expert systems); and the ongoing quest for strong AI (to build tomorrow's expert systems).

Whenever the target market is the consumer among the general public, to assume any degree of competence is to ask for trouble, even for products that incompetents have no legitimate excuse to be operating (e.g., motor vehicles, firearms, construction equipment). Even for the latter products, every effort is made in their engineering to make them as negligence-resistant and fail-safe as possible within the bounds of physics and of breaking even.

Gray areas (gradients between ant-vs-grasshopper and legitimate needs)

There are contexts and participants for which a gradient of RTFM (in)appropriateness exists. These are the gray areas between black and white. Some examples are given in the following sections.

Internet forums

An internet forum where users should read the FAQ before posting their questions is more likely to have a better signal-to-noise ratio than one that is filled with repetitive postings, and hence is more useful and more likely to attract continued participation. When evaluating whether it is acceptable to express sentiments like RTFM, one must consider the trade-off between maintaining the usability of a forum for its existing users, and making a forum welcoming to newcomers. The balance point for a particular forum depends on how general the audience is intended to be; but, as with the motor vehicle and firearm examples earlier, one must allow for the inevitability that people will find their way into the user population who do not meet the expectations. And unlike with motor vehicles and firearms (where unqualified users are committing an infraction by the very act of participating), there is nothing inappropriate about novices learning, for example, to play games or to use office software suites. In these cases, as in the technical support example, there is no reasonable expectation of minimum skill requirements. In such environments, frequent users of RTFM or GIYF responses are simply expressing elitism, stroking a personality flaw such as a need to tear others down to seek self-esteem. Their time could better be spent adding the question and answer to an FAQ, pointing the user to a helpful website, or simply not responding. This is especially true when, for example, it is not even clear which "manual" the receiver of the RTFM response should be reading. One of the most frequent criticisms of the open source community is lack of friendly support for newcomers. The Ubuntu Forums and LinuxQuestions.org, for instance, have instituted "no RTFM" policies to promote a welcoming atmosphere.

RTFM [and] "Go look on google" are two inappropriate responses to a question. If you don't know the answer or don't wish to help, please say nothing instead of brushing off someone's question. Politely showing someone how you searched or obtained the answer to a question is acceptable, even encouraged.

...

If you wish to remind a user to use search tools or other resources when they have asked a question you feel is basic or common, please be very polite. Any replies for help that contain language disrespectful towards the user asking the question, i.e. "STFU" or "RTFM" are unacceptable and will not be tolerated.

— Ubuntu Forums

Superior-to-subordinate feedback in workplaces or schools

Unlike with feedback between peers in workplaces or schools (where the ant-and-grasshopper model may often clearly apply), feedback from superiors to subordinates involves a degree of forbearance regarding incompetence. Not all incompetence is permanent, and not all infractions are grave. Managers and teachers have to walk a line and find the right balance. Laziness and incompetence are themselves teachable faults to some degree, which means that a superior has a responsibility "to help the asker to learn to help himself", even if it takes time and various attempts; but at some point, a line may be crossed, where fairness to others (and duty to other obligations) precludes any further "handholding" or "training wheels". In the workplace, the worker might have to be fired; in the school, the student may have to be disciplined (if able but unwilling) or (more likely) referred for special help or shifted into a different group of students. The school environment is more complex than the workplace, with greater responsibility on the part of the superior, because a schoolteacher always has a responsibility to recognize possible attention deficit or learning disability, and to refer the student for help in those areas (without which help, the student's inability to help himself is, to an important degree, not his own fault). In the business world, however, where the very employment itself is conditional on competence, the manager does not shoulder that responsibility beyond a basic degree of "giving a fair shake". Although there exists such a thing as improper termination, an RTFM/GIYF response from a manager tends to be more justified than one from a teacher. Even a teacher, though, is usually justified in saying, "If you didn't want to fail the quiz, then you should have done your homework instead of skateboarding/watching TV/etc."

Technological evolution catching workers off guard

The rapid advance of technology has caught many workers off guard, and they find that "the bar was raised and I didn't see it coming." Competencies that formerly were optional have become minimum requirements; certain knowledge, which they were formerly not responsible for having, has become a sine qua non, either in general culture or at least in the culture of a particular occupation. Common examples are digital literacy and initialism literacy in the workplace. Many workers today might agree that someone who doesn't know what the initalisms "FYI" or "OS" stand for is probably not competent to continue holding a white-collar job, because such jobs require a minimum degree of general knowledge, and initialisms such as those are no longer just slang for comp-sci geeks but rather have become common vocabulary in the general knowledge of all but IT illiterates. In other words, at some point in history, terms that used to be slang shift into basic vocabulary, and this principle applies to decades-old internet slang just as it has always applied to many other kinds of slang. If, on top of that, the asker also doesn't know that they should search its expansion before asking someone, then once again, there may be legitimate resentment in his subordinates that they must "manage upward" to such a mollycoddling degree, because the very GIYF principle itself has been shifting into the area of "general knowledge that is lacked only by incompetents." The degree of mollycoddling needed also indicates that the executives further up the line are themselves failing to do their jobs, because they have not provided adequate training or retraining (beyond mere on-the-job scrambling). Other example pieces of knowledge that used to be optional but have become a minimum requirement in the business world include basic file management. The grayer areas are ones where incompetence is currently stretching past annoyance toward negligence. The shade of gray for any particular skill (or lack thereof) depends on the occupation.

List of expurgated expansions

• Read the field manual (military contexts)
• Read the fine manual
• Read the freaking manual
• Read the full manual
• Read the full-on manual

List of similar initialisms

Encouraging the reading of the manual or other background information

• RTBM ("read the bloody manual") (In some countries, e.g., the UK and Australia, this is a fractionally more polite alternative with identical meaning)
• RTFA ("read the fucking article"—common on news forums such as Fark.com and Slashdot, where using "TFA" instead of "the article" has become a meme)
• RTFE ("read the fucking e-mail")
• RTFC ("read the fucking code" [also "reboot the fucking computer"])
• RTFSC ("read the fucking source code")
• RTFQ ("read the fucking question")
• RTFFAQ ("read the fucking frequently asked questions")
• UTFH ("use the fucking help")
• UTSL ("use the source, Luke", a play on the famous Star Wars quote, "Use the force, Luke", referring to freely available source code)

Encouraging the use of at least a basic search

• UTFG ("Use the fucking Google")
• JFGI ("just fucking Google it")
• JFWI ("just fucking Wiki it")
• JGIYN ("just Google it, you noob")
• STFG ("search the fucking Google" (the initials are consonant with STFU)
• STFW ("search the fucking Web") (the initials are consonant with STFU)
• WIDGI ("when in doubt, Google it"—also occasionally "WIDGIT")
• WABM ("write a better manual - an answer to UTFG when the manual is not written well")

See also

• Internet slang
• Unix manual ("man" pages)
• Usability engineering
• User interface design