<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: rtfm is dead, long live jfgi</title>
	<atom:link href="http://morgane.com/2007/03/11/rtfm-is-dead-long-live-jfgi/feed/" rel="self" type="application/rss+xml" />
	<link>http://morgane.com/2007/03/11/rtfm-is-dead-long-live-jfgi/</link>
	<description>All over the world</description>
	<pubDate>Mon, 01 Dec 2008 17:50:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Luke</title>
		<link>http://morgane.com/2007/03/11/rtfm-is-dead-long-live-jfgi/#comment-3363</link>
		<dc:creator>Luke</dc:creator>
		<pubDate>Sun, 11 Mar 2007 20:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://morgane.com/?p=317#comment-3363</guid>
		<description>LOL! Priceless!

I think the RTFM is sometimes appropriate in specific contexts. For example if a n00b pops into a general purpose chatroom or mailing list and ask a stupid question, he will probably get JFGI.

If he pops into a specific chatroom or list devoted to supporting/hacking specific software, or product it is entirely justified to tell him RTFM.

And I do read manuals sometimes. When I'm installing a new big piece of software or compiling it from source I usually print out the relevant readme files, flip through the quick through guide (if avaliable), have the manual booklet nearby if I need it or have my laptop nearby with googled up step-by-step tutorials.

I'm not the only one. The dude who deployed DFS, and tweaked load balancing rules and upgraded bunch of our Win2k3 servers at work had a check list, pages of hand written notes with him, a folder of stuff printed off Microsoft help sites and all kinds of other documentation. Hell, if he didn't have these things and refer to them I would probably smack him. This was a mission critical installation, and winging it was just not an option. :)

So I'd say RTFM is not dead - it just has a slightly more refined meaning nowadays. :)</description>
		<content:encoded><![CDATA[<p>LOL! Priceless!</p>
<p>I think the RTFM is sometimes appropriate in specific contexts. For example if a n00b pops into a general purpose chatroom or mailing list and ask a stupid question, he will probably get JFGI.</p>
<p>If he pops into a specific chatroom or list devoted to supporting/hacking specific software, or product it is entirely justified to tell him RTFM.</p>
<p>And I do read manuals sometimes. When I&#8217;m installing a new big piece of software or compiling it from source I usually print out the relevant readme files, flip through the quick through guide (if avaliable), have the manual booklet nearby if I need it or have my laptop nearby with googled up step-by-step tutorials.</p>
<p>I&#8217;m not the only one. The dude who deployed DFS, and tweaked load balancing rules and upgraded bunch of our Win2k3 servers at work had a check list, pages of hand written notes with him, a folder of stuff printed off Microsoft help sites and all kinds of other documentation. Hell, if he didn&#8217;t have these things and refer to them I would probably smack him. This was a mission critical installation, and winging it was just not an option. :)</p>
<p>So I&#8217;d say RTFM is not dead - it just has a slightly more refined meaning nowadays. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 14.532 seconds -->
