<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

	<title>Comments on: What's your tech writing bible?</title>
	<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible/</link>
	<description>Comments on Ask MetaFilter post What's your tech writing bible?</description>
	<pubDate>Thu, 12 Jun 2008 20:10:18 -0800</pubDate>
	<lastBuildDate>Thu, 12 Jun 2008 20:10:18 -0800</lastBuildDate>
	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>

	<item>
		<title>Question: What&apos;s your tech writing bible?</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible</link>	
		<description>What&apos;s your tech writing bible? &lt;br /&gt;&lt;br /&gt; So I&apos;m writing a tutorial for a bit of software.&lt;br&gt;
&lt;br&gt;
When it comes to the WHAT and WHY of it, I&apos;m all set &#8212; it&apos;s a tool for researchers in my field, so I could go on for hours about the ideas behind it.  But the HOW is proving tricky for me.  Listing the steps to follow to do X, or describing what button Y does, or explaining how to find Z in the output, just leaves me incoherent.&lt;br&gt;
&lt;br&gt;
I&apos;m looking for a good book (or website?) on technical writing that will explain how to write well about this stuff.  I&apos;m a writer first and a techie second, if that matters, and I don&apos;t mind spending some time reading &#8212; I&apos;d prefer something solid and comprehensive to a Fifteen Minute Guide For Dummies.  Suggestions?</description>
		<guid isPermaLink="false">post:ask.metafilter.com,2008:site.93950</guid>
		<pubDate>Thu, 12 Jun 2008 19:15:39 -0800</pubDate>
		<dc:creator>nebulawindphone</dc:creator>
		
			<category>techwriting</category>
		
			<category>technicalwriting</category>
		
			<category>books</category>
		
	</item> <item>
		<title>By: mattybonez</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1373874</link>	
		<description>You can&apos;t really go wrong with the &lt;a href=&quot;http://www.microsoft.com/MSPress/books/6074.aspx&quot;&gt;Microsoft Manual of Style&lt;/a&gt;. The first few chapters of the book discuss the &apos;how&apos; and should get you up to speed in 60-70 pages.The back of the book is a dictionary-type lookup that you can use for quick reference reference.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1373874</guid>
		<pubDate>Thu, 12 Jun 2008 20:10:18 -0800</pubDate>
		<dc:creator>mattybonez</dc:creator>
	</item><item>
		<title>By: mmoncur</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1373900</link>	
		<description>Ditto the MS Manual of Style, or maybe the Chicago Manual of Style.&lt;br&gt;
&lt;br&gt;
Better yet, the style guide from the publisher if there is one.&lt;br&gt;
&lt;br&gt;
I&apos;ve found my best resource for tech writing is just to have a few excellent tech books around to refer to. How did THEY do it?&lt;br&gt;
&lt;br&gt;
If your tutorial is for a publisher, web site, magazine, etc, I&apos;d read through lots of their other tutorials. Being similar to the style their readers are used to is more important than achieving some sort of stylistic perfection.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1373900</guid>
		<pubDate>Thu, 12 Jun 2008 20:36:53 -0800</pubDate>
		<dc:creator>mmoncur</dc:creator>
	</item><item>
		<title>By: nebulawindphone</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1373914</link>	
		<description>(Alas, there&apos;s no publisher and no style guide.  I&apos;m a grad student, and the whole team for this project is my advisor and two other students; as long as it gets written, none of them are particular about how the i&apos;s are dotted and the t&apos;s are crossed.  So I really do feel like I need some kind of outside guidance on what makes for good writing.)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1373914</guid>
		<pubDate>Thu, 12 Jun 2008 21:06:46 -0800</pubDate>
		<dc:creator>nebulawindphone</dc:creator>
	</item><item>
		<title>By: kindall</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1373982</link>	
		<description>The Microsoft style guide (or MSTP as it&apos;s called in Redmond) is really quite good. Sun&apos;s &lt;a href=&quot;http://www.amazon.com/exec/obidos/ASIN/0131428993/metafilter-20/ref=nosim/&quot;&gt;Read Me First!&lt;/a&gt; is also worth having, probably, though I haven&apos;t looked at it in a long time and haven&apos;t seen the second edition at all.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1373982</guid>
		<pubDate>Thu, 12 Jun 2008 23:00:58 -0800</pubDate>
		<dc:creator>kindall</dc:creator>
	</item><item>
		<title>By: Kadin2048</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1374036</link>	
		<description>Just tossing this one out there (we don&apos;t use a style guide at work, although we should):&lt;br&gt;
&lt;a href=&quot;http://oreilly.com/oreilly/author/stylesheet.html&quot;&gt;O&apos;Reilly Stylesheets and Style Guide&lt;/a&gt;&lt;br&gt;
&lt;br&gt;
It&apos;s focused more on the low-level elements of style, but might be what you&apos;re looking for.  I&apos;ve always found the O&apos;Reilly technical publications to be pretty easy to read.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1374036</guid>
		<pubDate>Fri, 13 Jun 2008 00:19:53 -0800</pubDate>
		<dc:creator>Kadin2048</dc:creator>
	</item><item>
		<title>By: pharm</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1374072</link>	
		<description>&lt;a href=&quot;http://www.amazon.com/exec/obidos/ASIN/020137921X/metafilter-20/ref=nosim/&quot;&gt;Bugs in writing&lt;/a&gt; by Lyn Dupr&#233; is worth reading, although I wouldn&apos;t make it my only reference.&lt;br&gt;
&lt;br&gt;
(For some reason this books seems to really rile some people: especially humourless types who regard any book that has a distinctive &apos;personal&apos; voice as being beyond the pale. The cats especially seem to set some of them off. Read the one star Amazon review for entertainment if nothing else.)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1374072</guid>
		<pubDate>Fri, 13 Jun 2008 01:08:38 -0800</pubDate>
		<dc:creator>pharm</dc:creator>
	</item><item>
		<title>By: pharm</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1374075</link>	
		<description>(Although that work may be too general for the original question.)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1374075</guid>
		<pubDate>Fri, 13 Jun 2008 01:09:38 -0800</pubDate>
		<dc:creator>pharm</dc:creator>
	</item><item>
		<title>By: Houstonian</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1374108</link>	
		<description>I agree that you should have the Microsoft Manual of Style. The latest version is Version 3. Microsoft had a difficult time getting it published in a timely manner, and so for a while offered it as a free download. It is still available for free download &lt;a href=&quot;http://faculty.washington.edu/farkas/TC407/MSTP-V3.pdf&quot;&gt;here&lt;/a&gt;.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1374108</guid>
		<pubDate>Fri, 13 Jun 2008 03:44:58 -0800</pubDate>
		<dc:creator>Houstonian</dc:creator>
	</item><item>
		<title>By: mbarryf</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1374139</link>	
		<description>(Shameless promotion for a free product)&lt;br&gt;
&lt;br&gt;
You can download my &quot;Creating Great User Documents&quot; Course totally free here:&lt;a href=&quot;http://www.greatuserdocs.com/DownloadCourse.htm&quot;&gt;http://www.greatuserdocs.com/DownloadCourse.htm&lt;/a&gt;&lt;br&gt;
&lt;br&gt;
The Course guides you in creating a great User Document for any kind of product.&lt;br&gt;
There are absolutely no strings attached, the site doesn&apos;t even ask for your name or e-mail address.  Take a look.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1374139</guid>
		<pubDate>Fri, 13 Jun 2008 05:15:25 -0800</pubDate>
		<dc:creator>mbarryf</dc:creator>
	</item><item>
		<title>By: catlet</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1374185</link>	
		<description>I&apos;m glad to see Sun&apos;s &lt;i&gt;Read Me First&lt;/i&gt; on the list. I think it&apos;s slightly more usable than the Microsoft manual, although both are here within hand&apos;s reach: stained with coffee, dogeared, and full of Post-It flags.&lt;br&gt;
&lt;br&gt;
&lt;b&gt;nebulawindphone&lt;/b&gt;, I&apos;m a tech editor by trade. If you want some input or a quick tutorial, feel free to MeFiMail me.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1374185</guid>
		<pubDate>Fri, 13 Jun 2008 06:33:42 -0800</pubDate>
		<dc:creator>catlet</dc:creator>
	</item><item>
		<title>By: fantabulous timewaster</title>
		<link>http://ask.metafilter.com/93950/Whats-your-tech-writing-bible#1375532</link>	
		<description>The focus isn&apos;t on software, but I have learned lots from Michael Alley&apos;s &quot;The Craft of Scientific Writing.&quot;</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.93950-1375532</guid>
		<pubDate>Sat, 14 Jun 2008 14:34:08 -0800</pubDate>
		<dc:creator>fantabulous timewaster</dc:creator>
	</item>
	</channel>
</rss>
