<?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: Muji Manifesto</title>
	<atom:link href="http://www.onemanwrites.co.uk/2008/01/15/muji-manifesto/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onemanwrites.co.uk/2008/01/15/muji-manifesto/</link>
	<description>musings on technical communications</description>
	<pubDate>Sun, 20 Jul 2008 15:09:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Kat</title>
		<link>http://www.onemanwrites.co.uk/2008/01/15/muji-manifesto/#comment-1840</link>
		<dc:creator>Kat</dc:creator>
		<pubDate>Sat, 19 Jan 2008 13:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/2008/01/15/muji-manifesto/#comment-1840</guid>
		<description>In technical writing, less has always been more. 

If you think it's about constructing complex sentences with flamboyant phrasing that shows off your literary skills, you are in the wrong job. 

The user needs to acquire the knowledge she needs to solve her problem pronto.</description>
		<content:encoded><![CDATA[<p>In technical writing, less has always been more. </p>
<p>If you think it&#8217;s about constructing complex sentences with flamboyant phrasing that shows off your literary skills, you are in the wrong job. </p>
<p>The user needs to acquire the knowledge she needs to solve her problem pronto.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
