<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description>This is the thought bubbles that come from me regarding my time at Hello Group during the course of the day.  Sometimes it might be something useful, but that depends entirely upon what you are trying to use it for.</description><title>ashley raiteri @ h3ll0 group</title><generator>Tumblr (3.0; @hello-ashley)</generator><link>http://hello.ashley.raiteri.net/</link><item><title>Process Diagrams are often ignoreable.  They rarely describe the...</title><description>&lt;img src="http://29.media.tumblr.com/PjKFluUdRmyagwhxMJl9rLcbo1_500.png"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;Process Diagrams are often ignoreable.  They rarely describe the &lt;i&gt;actual&lt;/i&gt; process and are almost never referenced in the working itself.  So why make them?  A good process diagram should tell you something you didn’t know before you looked at it.  And you should find that the diagram and reality come somewhere close to matching.&lt;/p&gt;</description><link>http://hello.ashley.raiteri.net/post/102219147</link><guid>http://hello.ashley.raiteri.net/post/102219147</guid><pubDate>Fri, 01 May 2009 06:30:00 -0400</pubDate><category>process-diagram</category><category>process</category><category>bad-example</category></item></channel></rss>

