If it doesn’t break, don’t change it
Posted by scmay on June 9, 2009
I noticed something wasn’t quite right in one of the database settings. Sure, it won’t be obvious and it will never get spotted on the surface if everything is entered via the system, but if you were to manually enter via database, sooner or later some error is going to happen. I was thinking of fixing it, but then I remembered a colleague once said, “If it doesn’t break, don’t change it” (it might become worse after changing it)
Which was what happened to my VS2005, which was running pretty slow and I decided to ‘clean’ the registry manager, till I realised that ‘cleaning’ meant removing most of the keys (which meant that the program was really stupid to identify which keys should be removed and which shouldn’t). Sad to say, Resharper could not work on my VS2005 and also made my VS weird. (Eg I cannot add a new file in a project)
VS2003 went through the whole clean-up-and-reinstall process, but since I was mainly working on VS2005 and the reinstall usually takes up a lot of time I had to do without Resharper for sometime. Strangely, I managed to install Resharper again the other day after months without it (It did not work previously, clean-and-install, contacting Helpdesk and etc)
