📄 00000037.htm
字号:
<HTML><HEAD> <TITLE>BBS水木清华站∶精华区</TITLE></HEAD><BODY><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER>发信人: linuxrat (叫我老鼠错不了), 信区: Linux <BR>标 题: 呵呵, 新手重复提问有个说法了[FWD] <BR>发信站: BBS 水木清华站 (Mon Jan 17 14:26:47 2000) <BR> <BR> URL: www.linuxnewbie.org <BR>=======Begin============= <BR> The Linux Newbie Replies: WFM? <BR> Written By: Ray Woodcock <BR> <BR> Skilled computer users nowadays often tire of newbies asking questions <BR> that are fully answered in the available documentation. "Why are you <BR> asking me this?" they ask. "Why don't you Read The Fricking Manual?" <BR> That phrase, oft repeated (usually with a stronger F word), has formed <BR> a rut in the earth and is now known simply by the acronym RTFM. For <BR> more detailed documentation of this acronym, see <BR> <A HREF="http://harmless.rrnet.com/~glen/Unix/rtfm.html.">http://harmless.rrnet.com/~glen/Unix/rtfm.html.</A> <BR> (faint, 我看了这个网页差点晕倒......我放在文章后面了, 自己看吧. ft) <BR> <BR> This acronym deserves a second look, however. Let us think back to its <BR> roots. Some of us may remember the corporate heyday of the 1970s and <BR> 1980s, when managers would put programmers on the spot with their own <BR> famous acronym, DYRTM (short for "Didn't You Read The Memo?"). In <BR> those days, many managers were liberal arts majors, journalism <BR> graduates, and other verbose individuals who could easily crank out <BR> memoranda twice as fast as the programmers would read them, and about <BR> four times as fast as any ordinary individual could understand and <BR> apply them. So it was child's play for such managers to concoct new <BR> policies and procedures, and then yell at the programmers for failing <BR> to memorize and worship these endless piles of engraved dogma. <BR> <BR> Yet observe how the worm turns! With the aid of this snide DYRTM <BR> acronym, management won the battle -- but it lost the war. Computer <BR> people took careful note of the way in which a simple, honest question <BR> could thus be turned aside with a smart-ass bureaucratic response. And <BR> now that the rug is getting worn out in the other direction, with <BR> managers traipsing down the hall for advice from computer gurus, we <BR> hear the mighty response: Ha! Take that, capitalist pig! RTFM! <BR> <BR> Of course, programmers are generally more reasonable and logical than <BR> their managers. So rather than get dragged into another generation of <BR> tug-o-war with the so-called managerial elite, the discriminating <BR> programmer might consider several regards in which RTFM somewhat <BR> overshoots the mark. The general idea, here, is to observe that cute <BR> phrases, like profanity, are only useful when they are reserved for <BR> radical souls who know how to make a point with them. When everyone <BR> starts saying "Way, dude!" or "Go to hell!" or "RTFM!" <BR> indiscriminately, these terms begin to lose their impact, and someone <BR> must think of new verbal devices to take their place. <BR> <BR> Let us consider, then, the following instances in which a newbie, upon <BR> being accosted with a shout of "RTFM," might validly retort by saying <BR> WFM: <BR> <BR> 1. What Fricking Manual? In the late 1980s and early 1990s, <BR> WordPerfect had a marvelous manual and excellent tech support. By <BR> contrast, Microsoft assigned the production of manuals to a separate <BR> division, which would charge a separate price for them. This had great <BR> efficiency from the producer's point of view, but most users <BR> predictably did not wish to spend $30-50 or more for a manual in <BR> addition to the already high prices they were paying for Microsoft <BR> software. (Unfortunately, but not surprisingly, the so-called online <BR> help files that accompany Microsoft programs are often not as helpful <BR> as the books that Microsoft would like to sell you.) So for casual <BR> users of many Microsoft programs, and of other software that follows <BR> Microsoft's concept of documentation, it became much less obvious that <BR> a person could or should find and consult a manual. <BR> <BR> 2. Which Fricking Manual? The documentation for Linux and its <BR> affiliates, associates, parents, subsidiaries, siblings, friends, <BR> neighbors, and offspring (including VI, dselect, Emacs, X-windows, <BR> bash, GNU, KDE, and four bazillion other Linux-related programs and <BR> variations) would now fill Yankee Stadium; and for newbies staring at <BR> a Linux command prompt, it is not always clear which of those <BR> commands, shells, or programs is (or should be) at work. Given that, <BR> "RTFM" is often inefficient advice. Users will reasonably resist the <BR> idea that they should spend four days seeking the answer to a <BR> relatively trivial question. It is not crazy to suggest that the <BR> expert who has the answer should provide it, or should point to the <BR> best source of documentation for questions like that one. Indeed, <BR> "RTFM" may aggravate the problem in some cases, where the user is <BR> asking dumb questions because of some emotional problem (e.g., lack of <BR> confidence that s/he really can make this program work). In such <BR> cases, a harsh reply is worse than none at all. To those who come down <BR> hard on newbies, I say, Lighten up! And be glad that they don't make <BR> you read the manual when you go to the hospital for an operation! <BR> <BR> 3. Why not write a real Fricking Manual? After fifteen years of <BR> assembling PCs, I am here to testify that few things are more amusing <BR> than being told, by a native Arabic speaker at some PC clone shop, <BR> that I should just RTFM, which happens to have been written by a <BR> native Chinese speaker. Even today, amazingly, there are still <BR> producers of computer hardware who have not yet discovered that <BR> journalism majors -- the type who used to become managers -- are <BR> available cheap, and in many cases would be delighted to justify their <BR> liberal arts eductions by rewriting the company's impenetrable, alien <BR> manuals and Web pages in scintillating, entertaining, thoroughly <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -