soens
Together we keep the universe balanced.

Yes, but...I'm always looking for the "magic bullet" that makes some systems work almost flawlessly, while other people experience strings of issues. I've noticed there are some people who experience a serial line of problems and although in some cases it's pilot error, in some cases it's most definitely not. Is there some "poison plug-in?" Some background service that interferes? Pieces of Norton left over from a demo that was installed on the C: drive and never completely removed (as happened with my mother's computer - deleting every trace of Norton make it like a new machine)? There has to be something that accounts for these disparities.
 
I do try to follow good practices, and I think that has a lot to do with why I can run SONAR for hours on end without incident. But which of those "good practices" is the crucial one that makes the difference? I wish I knew so I could tell others.

Most of the things I experience are minor and don't really affect the final outcome of a project. But on the way to the finish line, when they pop up causing distractions I report many of them in case others are experiencing the same thing. If no one responds with a "me too" or a solution, I chalk it up to being my very own specialized experience that will soon be forgotten.
 
No piece of software is without it's own set of issues. The ones with the most issues are the ones we use the most. In spite that we keep using them because they ultimately get us where we want to go.