<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>2moroDocs &#187; New Generation Users — 2moroDocs</title>
	<atom:link href="http://www.2morodocs.com/tag/new-generation-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.2morodocs.com</link>
	<description>New-age technical communication trends</description>
	<lastBuildDate>Tue, 07 Sep 2010 19:10:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>5 Reasons to Write Procedures in Twitter</title>
		<link>http://www.2morodocs.com/2010/01/5-reasons-to-write-procedures-in-twitter/</link>
		<comments>http://www.2morodocs.com/2010/01/5-reasons-to-write-procedures-in-twitter/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 02:25:32 +0000</pubDate>
		<dc:creator>Julie Norris</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[New Generation Users]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Real-time]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.2morodocs.com/?p=542</guid>
		<description><![CDATA[
			
				
			
		

Recently, I’ve been exploring the need for writing procedures in real-time, focusing on Twitter in particular. This is the fourth post in the series. In my last post, I was asked by Larry Kunz in a comment for thoughts on situations in which one might write procedures in Twitter. Five come to mind; I’ve described [...]]]></description>
		<wfw:commentRss>http://www.2morodocs.com/2010/01/5-reasons-to-write-procedures-in-twitter/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>
