This post originated from an RSS feed registered with Web Buzz by Josh Baltzell. Original Post: Instructions for ruining a perfectly good PC Feed Title: ShortDomainName.com Feed URL: http://www.contegix.com/Rss.aspx Feed Description: Weblog of Josh Baltzell. Focusing on the computer industry and .NET programming related news. I like to get involved on the discussions wherever they are. Latest Web Buzz Posts Latest Web Buzz Posts by Josh Baltzell Latest Posts From ShortDomainName.com

When letting your computer go for the sake of “productivity” please take the following steps in to consideration:

1:  Reboot only when nothing works anymore.  As an application developer using your own PC as a server for your Database and for IIS I suggest occasionally restart SQL and IIS when you computer runs slower than your mom's PC.

2:  Install as many small applications for testing as you possibly can.  Please refrain from uninstalling these applications until you can no longer consider your PC useful.  Your time is much more precious now than it will be in the future, so screw future you.

3:  Run Windows Update on a regular basis, but do not reboot even if it tells you too.  This will help with system stability.

4:  When beginning work with Visual Studio.NET you may have installed a Beta version first.  After that Beta ended you should have installed the trial version of Visual Studio.NET 2002 along with the old Beta Version.  Now with two version on the drive feel free to order an MSDN subscription so you can install yet another edition of Visual Studio.NET on your PC.

5:  When managing a local IIS installation make sure you do not name any folders clearly.  This is the most efficient way to make folders quickly so that the job is done ASAP.

Now that you have the steps you need you can begin to assemble the software build of the machine I am fighting with now.  IIS seems to have grown tired of running the debugging that goes with VS.NET.  So now I have had the enjoyment of uninstalling 3 versions of VS.NET to reinstall one correct one.

Now VS.NET is EXTRA slow to open too.  That is an added bonus.  So I reinstalled IIS, open VS.NET and it told me IIS was using the wrong version of the framework.  So now I am doing windows update and rebooting to see if that fixes it without me changing anything in IIS.

Fun.