If it ain't broke, what is there to fix?

For all the IT wise-guys out there: I thought I'd fix it. Problem was, it wasn't broke. So in reality, I broke it -- cause there wasn't anything to fix. Could this be considered to be another example of the "Chicken-Egg-Syndrome"? What comes first: the PC that works - in one way or another -- ?, or the PC that works --- in one way or another? It is just the program that changes that may be more sluggish... before and after the Fixing. At least now, I know why: because I fixed it.
Now if my PC and I could get an alliance like the recently announced Microsoft - Nortel one going, that would something, wouldn't it? An alliance between "communication" and "IT". I take the role of being the communicator and my PC the one of the IT (we are both too stubborn in our own roles to try it the other way around). Now wouldn't that be a perfect world? Guess I should wait first, to see how the big alliance works before trying it out in my little world.