<?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: Applying Visualization to Software Development</title>
	<atom:link href="http://blogs.infinite-x.net/2008/05/30/applying-visualization-to-software-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.infinite-x.net/2008/05/30/applying-visualization-to-software-development/</link>
	<description>Knowledge found and lost while working with Microsoft CRM</description>
	<pubDate>Fri, 21 Nov 2008 06:09:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Bill Babcock</title>
		<link>http://blogs.infinite-x.net/2008/05/30/applying-visualization-to-software-development/#comment-829</link>
		<dc:creator>Bill Babcock</dc:creator>
		<pubDate>Sun, 01 Jun 2008 17:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.infinite-x.net/2008/05/30/applying-visualization-to-software-development/#comment-829</guid>
		<description>I think it's the only way people can solve any complex problem. We don't form completely complex solutions, a lot of the process is unconscious and takes time. I think the "flashes of brilliance" come from relatively long periods of processing a problem and looking at various ways to solve it. Of   course there is also the knowledge and insight gained by working though the problem, but this tends to make the project larger and more difficult because it adds scope creep elements. You learn new things as the project progresses and it's hard not to incorporate the learnings. 

A trivial but fun example: &lt;a&gt; http://www.mysoftwarefilm.com/ &lt;/a&gt;  This started out as a movie theme-based landing page for Intel's Software Partner Program and morphed into this. Yikes.</description>
		<content:encoded><![CDATA[<p>I think it&#039;s the only way people can solve any complex problem. We don&#039;t form completely complex solutions, a lot of the process is unconscious and takes time. I think the &#034;flashes of brilliance&#034; come from relatively long periods of processing a problem and looking at various ways to solve it. Of   course there is also the knowledge and insight gained by working though the problem, but this tends to make the project larger and more difficult because it adds scope creep elements. You learn new things as the project progresses and it&#039;s hard not to incorporate the learnings. </p>
<p>A trivial but fun example: <a> </a><a href="http://www.mysoftwarefilm.com/" rel="nofollow">http://www.mysoftwarefilm.com/</a>   This started out as a movie theme-based landing page for Intel&#039;s Software Partner Program and morphed into this. Yikes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mitch</title>
		<link>http://blogs.infinite-x.net/2008/05/30/applying-visualization-to-software-development/#comment-827</link>
		<dc:creator>mitch</dc:creator>
		<pubDate>Sun, 01 Jun 2008 17:23:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.infinite-x.net/2008/05/30/applying-visualization-to-software-development/#comment-827</guid>
		<description>Dodd, I like your "3 ains" technique - and I totally agree.</description>
		<content:encoded><![CDATA[<p>Dodd, I like your &#034;3 ains&#034; technique - and I totally agree.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dodd</title>
		<link>http://blogs.infinite-x.net/2008/05/30/applying-visualization-to-software-development/#comment-823</link>
		<dc:creator>Dodd</dc:creator>
		<pubDate>Fri, 30 May 2008 18:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.infinite-x.net/2008/05/30/applying-visualization-to-software-development/#comment-823</guid>
		<description>Funny you should post this, as I have been thinking about this a lot myself, more specifically the principal of Ockham's Razor and how this can be applied to CRM. Ultimately, Simplicity in design is easier to maintain, explain, and retain (I tend to refer to these as the "3 ains"), though simplicity in design is not always the easiest to create.

As a avid pool shooter, I always see the angles on the table before lining up a shot. Then, before hitting the cue ball, I visualize the many ways the balls could go as I move the stick. Once I'm satisfied, I take the shot. 90% of the time I make it to the pocket.

I tend to do the same thing before I write anything. If it's an e-mail, I picture having a dialog with my client or co-worker. If it's a blog, I tend to picture it as if I were giving a demo in front of an audience. This way, I'm not writing, but rather listening and copying down the dialog in my head.

I prefer to pace about while I visualize. I'm not sure why, but I can see things clearer when I'm active, or performing an activity.</description>
		<content:encoded><![CDATA[<p>Funny you should post this, as I have been thinking about this a lot myself, more specifically the principal of Ockham&#039;s Razor and how this can be applied to CRM. Ultimately, Simplicity in design is easier to maintain, explain, and retain (I tend to refer to these as the &#034;3 ains&#034;), though simplicity in design is not always the easiest to create.</p>
<p>As a avid pool shooter, I always see the angles on the table before lining up a shot. Then, before hitting the cue ball, I visualize the many ways the balls could go as I move the stick. Once I&#039;m satisfied, I take the shot. 90% of the time I make it to the pocket.</p>
<p>I tend to do the same thing before I write anything. If it&#039;s an e-mail, I picture having a dialog with my client or co-worker. If it&#039;s a blog, I tend to picture it as if I were giving a demo in front of an audience. This way, I&#039;m not writing, but rather listening and copying down the dialog in my head.</p>
<p>I prefer to pace about while I visualize. I&#039;m not sure why, but I can see things clearer when I&#039;m active, or performing an activity.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
