<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>Technically Speaking</title>
	<link>http://blog.paulpehrson.com</link>
	<description>Paul Pehrson's technical writing blog</description>
	<lastBuildDate>Tue, 16 Mar 2010 18:27:04 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Review of MadCap Flare V6</title>
		<description><![CDATA[If you are a technical communicator who pays attention to the latest releases of help authoring tools, you probably heard that MadCap Software released a new version of its flagship product, MadCap Flare.
I’ve been using Flare V6 for a couple of months now, and this review is to give you an end user’s review of [...]]]></description>
		<link>http://blog.paulpehrson.com/2010/03/15/review-of-madcap-flare-v6/</link>
			</item>
	<item>
		<title>Why documentation should go through QA</title>
		<description><![CDATA[If you&#8217;ve ever wondered if user documentation should go through the same QA cycle as the code, here is an answer in an example from Kids.Woot.com:

&#8220;Nothing good in life is easy. So it is with the AMAV 9002Motorcrafts Locomotive Kit. For one thing, the included directions are wrong: you must mount the motor with the opposite orientation [...]]]></description>
		<link>http://blog.paulpehrson.com/2010/03/15/why-documentation-should-go-through-qa/</link>
			</item>
	<item>
		<title>MadCap Flare V6 Released!</title>
		<description><![CDATA[MadCap Software today released Flare V6, and it is pretty cool.
I&#8217;m still working on a post to give you the details to help you decide if you should upgrade your existing Flare project to V6 (which I&#8217;ve been previewing for about a month), but alas, with work deadlines that post will have to wait until [...]]]></description>
		<link>http://blog.paulpehrson.com/2010/03/02/madcap-flare-v6-released/</link>
			</item>
	<item>
		<title>Running for Office</title>
		<description><![CDATA[I&#8217;m running for the office of Chapter President in the Intermountain chapter of the Society for Technical Communication. You can see my candidate statement on the IM-STC website.
Wish me luck!
]]></description>
		<link>http://blog.paulpehrson.com/2010/02/19/running-for-office/</link>
			</item>
	<item>
		<title>Skuut on over to great customer serivce</title>
		<description><![CDATA[My three year old loves to play outside. About a year ago, we got him a Skuut, but because we lived in a condo, he only rode it once or twice last year. 
I loved the Skuut when we bought it because of its all wood design, and the way it teaches young kids to [...]]]></description>
		<link>http://blog.paulpehrson.com/2010/02/03/skuut-on-over-to-great-customer-serivce/</link>
			</item>
	<item>
		<title>No geeking out over the iPad here</title>
		<description><![CDATA[The makers of the iPhone, Apple, today announced a &#8220;revolutionary&#8221; device: a tablet computer they call iPad. Now, normally I&#8217;m a big fan of things Apple. I have an iPod touch (don&#8217;t want the service contract or wireless provider of the iPhone), and I love it. So you might be expecting me to be geeking [...]]]></description>
		<link>http://blog.paulpehrson.com/2010/01/27/no-geeking-out-over-the-ipad-here/</link>
			</item>
	<item>
		<title>Lassie is no more</title>
		<description><![CDATA[Back in 2004 we received a much needed gift: a little red truck named Lassie. Lassie was a 1984 red Toyota pick up truck that got her name because when my in-laws owned her, she was stolen several times, yet every time she came back home (the police found the truck and brought it back). [...]]]></description>
		<link>http://blog.paulpehrson.com/2010/01/26/lassie-is-no-more/</link>
			</item>
	<item>
		<title>Intellectual Property Responsibilities of Content Developers</title>
		<description><![CDATA[As a technical writer, I develop content for the applications I&#8217;m supporting. Often that includes designing content, images, and multi-media to provide the best user experience possible. As content developers, however, we have a responsibility (both legal and moral) to ensure that the content we are using is being used properly and legally.
We live in [...]]]></description>
		<link>http://blog.paulpehrson.com/2009/10/13/intellectual-property-responsibilities-of-content-developers/</link>
			</item>
	<item>
		<title>Analysis of Team Design Review</title>
		<description><![CDATA[Probably most of you don&#8217;t know that I changed jobs recently, which is part of the reason I&#8217;ve been posting so infrequently. When you change jobs there is so much to learn, and it takes time.
One of the benefits of my new job is that I&#8217;m working with an impressive team. I have great respect [...]]]></description>
		<link>http://blog.paulpehrson.com/2009/10/07/design-review/</link>
			</item>
	<item>
		<title>The STC Crisis: the take of a &#8220;young&#8221; writer</title>
		<description><![CDATA[As  a &#8220;young&#8221; technical writer, I thought I might share some of my feelings on the STC crisis.
First, a little background on me. I knew while I was in college that I wanted to be a technical writer after graduation. I switched to an English major for that purpose, and picked classes that gave me [...]]]></description>
		<link>http://blog.paulpehrson.com/2009/06/22/the-stc-crisis-the-take-of-a-young-writer/</link>
			</item>
</channel>
</rss>
