<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SolidWorks Tip:  Time to upgrade!</title>
	<atom:link href="http://www.rickyjordan.com/2006/10/solidworks_tip_.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.rickyjordan.com/2006/10/solidworks_tip_.html</link>
	<description>SolidWorks, The CAD Industry, &#38; More!</description>
	<lastBuildDate>Mon, 15 Mar 2010 23:12:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ijokasu</title>
		<link>http://www.rickyjordan.com/2006/10/solidworks_tip_.html/comment-page-1#comment-2074</link>
		<dc:creator>ijokasu</dc:creator>
		<pubDate>Thu, 30 Apr 2009 21:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://74.220.219.56/~rickyjor/2006/10/solidworks-tip-time-to-upgrade.html#comment-2074</guid>
		<description>thanks for the advice</description>
		<content:encoded><![CDATA[<p>thanks for the advice</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ijokasu</title>
		<link>http://www.rickyjordan.com/2006/10/solidworks_tip_.html/comment-page-1#comment-1541</link>
		<dc:creator>ijokasu</dc:creator>
		<pubDate>Thu, 30 Apr 2009 15:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://74.220.219.56/~rickyjor/2006/10/solidworks-tip-time-to-upgrade.html#comment-1541</guid>
		<description>thanks for the advice</description>
		<content:encoded><![CDATA[<p>thanks for the advice</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Chastine</title>
		<link>http://www.rickyjordan.com/2006/10/solidworks_tip_.html/comment-page-1#comment-45</link>
		<dc:creator>Chris Chastine</dc:creator>
		<pubDate>Tue, 18 Dec 2007 08:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://74.220.219.56/~rickyjor/2006/10/solidworks-tip-time-to-upgrade.html#comment-45</guid>
		<description>Thanks for the great advice Ricky - good stuff, but it makes me wonder something. Even before the upgrade there is the process of testing the new software to see if it&#039;s ready to be implemented. Do you have a set of procedures you use to test the software?
I typically try to time it so I start working on a new project while testing. That way I get some real world examples and can see how the new software handles it. Obviously this can&#039;t always be done since new projects don&#039;t always creep up at the most opportune time.
So what do you do to test the software?
</description>
		<content:encoded><![CDATA[<p>Thanks for the great advice Ricky &#8211; good stuff, but it makes me wonder something. Even before the upgrade there is the process of testing the new software to see if it&#8217;s ready to be implemented. Do you have a set of procedures you use to test the software?<br />
I typically try to time it so I start working on a new project while testing. That way I get some real world examples and can see how the new software handles it. Obviously this can&#8217;t always be done since new projects don&#8217;t always creep up at the most opportune time.<br />
So what do you do to test the software?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Chastine</title>
		<link>http://www.rickyjordan.com/2006/10/solidworks_tip_.html/comment-page-1#comment-846</link>
		<dc:creator>Chris Chastine</dc:creator>
		<pubDate>Tue, 18 Dec 2007 06:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://74.220.219.56/~rickyjor/2006/10/solidworks-tip-time-to-upgrade.html#comment-846</guid>
		<description>Thanks for the great advice Ricky - good stuff, but it makes me wonder something. Even before the upgrade there is the process of testing the new software to see if it&#039;s ready to be implemented. Do you have a set of procedures you use to test the software?&lt;br&gt;I typically try to time it so I start working on a new project while testing. That way I get some real world examples and can see how the new software handles it. Obviously this can&#039;t always be done since new projects don&#039;t always creep up at the most opportune time.&lt;br&gt;So what do you do to test the software?</description>
		<content:encoded><![CDATA[<p>Thanks for the great advice Ricky &#8211; good stuff, but it makes me wonder something. Even before the upgrade there is the process of testing the new software to see if it&#39;s ready to be implemented. Do you have a set of procedures you use to test the software?<br />I typically try to time it so I start working on a new project while testing. That way I get some real world examples and can see how the new software handles it. Obviously this can&#39;t always be done since new projects don&#39;t always creep up at the most opportune time.<br />So what do you do to test the software?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
