<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Ricky Jordan's Blog - Latest Comments in SolidWorks Tip:  Time to upgrade!</title><link>http://rickyjordan.disqus.com/</link><description>CAD Blog featuring SolidWorks related Reviews, Tips, Tricks, News, &amp; Videos.  Blog is hosted by Ricky Jordan, CSWP, President, North Alabama SolidWorks User Group (NASWUG), Huntsville, AL</description><language>en</language><lastBuildDate>Thu, 30 Apr 2009 12:46:01 -0000</lastBuildDate><item><title>Re: SolidWorks Tip:  Time to upgrade!</title><link>http://www.rickyjordan.com/2006/10/solidworks_tip_.html#comment-8867845</link><description>thanks for the advice</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ijokasu</dc:creator><pubDate>Thu, 30 Apr 2009 12:46:01 -0000</pubDate></item><item><title>Re: SolidWorks Tip:  Time to upgrade!</title><link>http://www.rickyjordan.com/2006/10/solidworks_tip_.html#comment-1789667</link><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'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't always be done since new projects don't always creep up at the most opportune time.&lt;br&gt;So what do you do to test the software?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Chastine</dc:creator><pubDate>Tue, 18 Dec 2007 03:42:37 -0000</pubDate></item></channel></rss>