How about you folks? Are you simply more tolerant of "normal" computer BS than i am or are you all just somehow better off?
Part of it is surely my working methods. Somehow, i am able to find bugs that no one else finds (or gives a crap about). It makes me a great beta tester, if you really do want to acknowledge and eliminate bugs (mostly, my reports are acknowledged, documented, and then considered unimportant and "will not fix").
i am aware of the "inherent complexity" of computers and the process of testing with the politics involved (see "will not fix" above and add "cannot reproduce"). Consequentially, i learned, way back in 2000, to stop customizing Windows with plug-ins and even to stop trying to USE many built-in customizations (keep defaults) because they eventually fail somewhere for lack of testing and cause system problems. So i don't really do that.
i have always built my own systems by choosing best of breed components (so it seemed) and now i have sworn to NEVER EVER build a PC EVER again (it's like voodoo & every geek online has the magic answer to all your problems: "you bought the wrong [n]" and "you're doing it wrong"). i was a tech guy most of my employed life (and even a tech guy when i became a trainer), fixing everyone else's computer problems, and hating to maintain my own systems instead of using them as tools (because i've long grown out of the computer BEING the hobby, though it seems some great sin of computing to want to not have to do "regular maintenance" on your computer because it's just like a car -NO IT'S NOT!). Tech people exist so that everyone else can get some work done sometimes. i can't afford to hire an IT department to allow me to walk away from misbehaving apps or hardware, demanding "it better work by the time i come back from lunch!"
i'm tempted to say that i have more success using Apple products as actual appliances and tools, instead of tech nightmares, but i have some annoying problems there too. For example: Logic is designed such that plug in instruments aren't active until they're first demanded to produce audio. You start the track, it plays, you get to a region where an instrument starts for the first time, the CPU spikes and the engine drops out. You have to start over again. This is known in the community, but clearly there are enough people who do not suffer drop outs because it's very popular in studios with many published professionals swearing by it (are they just putting up with this annoyance over and over and not being bothered by it???).
It's not just audio. i experienced the same exact thing, maybe worse, with 3D graphics projects (gaming has been mostly ok; word processing has always been a cakewalk, no topical pun intended).
So what's up, folks? Is anyone with me, or am i really the singled-out, alien, crazy, conspired-against pariah of computing? i already know the simple answers, so please don't use them here if that's all you got