<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Technical Writer vs. Daydreamer: Not So Distant After All</title>
	<atom:link href="http://www.gryphonmountain.net/2008/03/technical-writer-vs-daydreamer-not-so-distant-after-all/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gryphonmountain.net/2008/03/technical-writer-vs-daydreamer-not-so-distant-after-all/</link>
	<description>Technical Communication and Other Writing Topics (by Ben Minson)</description>
	<lastBuildDate>Mon,  6 Sep 2010 20:49:16 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Ben</title>
		<link>http://www.gryphonmountain.net/2008/03/technical-writer-vs-daydreamer-not-so-distant-after-all/comment-page-1/#comment-65</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sat, 29 Mar 2008 17:11:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/archives/uncategorized/technical-writer-vs-daydreamer-not-so-distant-after-all#comment-65</guid>
		<description>I agree that generally, we want to avoid something like humor in documentation, but I think it also depends on the nature of the product you&#039;re working on. If you&#039;re documenting a product that is all about fun, then I think it wouldn&#039;t be out of line. One way to look at it is whether humor or lightheartedness would get in the way.

That said, I can&#039;t think of a set of documentation or instructions I&#039;ve used recently that was anything but straightforward and dry. That&#039;s probably why tech writers have the reputation that we do. Instructions for games probably come the closest to being informal. Using humor in some form or degree may help to catch readers&#039; interest, but you have to know your audience. Examples of casual or lighthearted documentation would be interesting to see, so feel free to post them here if you come across any.</description>
		<content:encoded><![CDATA[<p>I agree that generally, we want to avoid something like humor in documentation, but I think it also depends on the nature of the product you&#8217;re working on. If you&#8217;re documenting a product that is all about fun, then I think it wouldn&#8217;t be out of line. One way to look at it is whether humor or lightheartedness would get in the way.</p>
<p>That said, I can&#8217;t think of a set of documentation or instructions I&#8217;ve used recently that was anything but straightforward and dry. That&#8217;s probably why tech writers have the reputation that we do. Instructions for games probably come the closest to being informal. Using humor in some form or degree may help to catch readers&#8217; interest, but you have to know your audience. Examples of casual or lighthearted documentation would be interesting to see, so feel free to post them here if you come across any.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan</title>
		<link>http://www.gryphonmountain.net/2008/03/technical-writer-vs-daydreamer-not-so-distant-after-all/comment-page-1/#comment-63</link>
		<dc:creator>Susan</dc:creator>
		<pubDate>Sat, 29 Mar 2008 13:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/archives/uncategorized/technical-writer-vs-daydreamer-not-so-distant-after-all#comment-63</guid>
		<description>Generally, technical writers have to avoid humor in documentation at all cost (Rule #1: Never make users feel stupid) . . .  but wouldn&#039;t it be fun if we could be creative and add some humor hidden in the help manual for the heck of it?   Software developers add easter eggs, why can&#039;t we do something similar.</description>
		<content:encoded><![CDATA[<p>Generally, technical writers have to avoid humor in documentation at all cost (Rule #1: Never make users feel stupid) . . .  but wouldn&#8217;t it be fun if we could be creative and add some humor hidden in the help manual for the heck of it?   Software developers add easter eggs, why can&#8217;t we do something similar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timber</title>
		<link>http://www.gryphonmountain.net/2008/03/technical-writer-vs-daydreamer-not-so-distant-after-all/comment-page-1/#comment-37</link>
		<dc:creator>Timber</dc:creator>
		<pubDate>Sat, 22 Mar 2008 21:58:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/archives/uncategorized/technical-writer-vs-daydreamer-not-so-distant-after-all#comment-37</guid>
		<description>I would compare the challenges of Technical Writing to be similar to literary analysis type papers.  The paper&#039;s topic may be fairly dry analytical, but there must be an element of creativity in the writing style, or no one will want to read it.  The challenge is keeping the ideas clear and your style professional while keeping the reader engaged.  You do well, Ben.  I think your voice is formal, but also amusing and amused.  I like that you laugh at yourself.</description>
		<content:encoded><![CDATA[<p>I would compare the challenges of Technical Writing to be similar to literary analysis type papers.  The paper&#8217;s topic may be fairly dry analytical, but there must be an element of creativity in the writing style, or no one will want to read it.  The challenge is keeping the ideas clear and your style professional while keeping the reader engaged.  You do well, Ben.  I think your voice is formal, but also amusing and amused.  I like that you laugh at yourself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.gryphonmountain.net/2008/03/technical-writer-vs-daydreamer-not-so-distant-after-all/comment-page-1/#comment-32</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sat, 22 Mar 2008 16:45:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/archives/uncategorized/technical-writer-vs-daydreamer-not-so-distant-after-all#comment-32</guid>
		<description>Thanks, Tom. I don&#039;t think I explored the topic very deeply, however. Sounds like future blog material...</description>
		<content:encoded><![CDATA[<p>Thanks, Tom. I don&#8217;t think I explored the topic very deeply, however. Sounds like future blog material&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom johnson</title>
		<link>http://www.gryphonmountain.net/2008/03/technical-writer-vs-daydreamer-not-so-distant-after-all/comment-page-1/#comment-21</link>
		<dc:creator>tom johnson</dc:creator>
		<pubDate>Fri, 21 Mar 2008 02:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/archives/uncategorized/technical-writer-vs-daydreamer-not-so-distant-after-all#comment-21</guid>
		<description>Ben, I lke your perspective. I&#039;d never thought of creativity transferring into problem-solving slills in technical writing. I definitely agree with you.</description>
		<content:encoded><![CDATA[<p>Ben, I lke your perspective. I&#8217;d never thought of creativity transferring into problem-solving slills in technical writing. I definitely agree with you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
