This is probably the root of a lot of the disagreements I am starting to have with a lot of the hardcore users here. Even the whole Apple stuff I'm talking about now. I'm changing. I recognize it. I love computers and technology, but I'm not willing to spend hours anymore trying to do simple things because programmers won't make a button for it.
-superboyac
+1
I'm not quite there yet. But I'm a lot more
there than I used to be.
In my case, I'm probably more tolerant than I should be because computers are something "I do" as opposed to something "I do something with." I'm an IT systems person, which is roughly akin to being a perpetual bridesmaid.
End-users ask me what games I recommend, or "what's a good way to (fill in the blank)" - and I have to tell them I really am not the best person to ask. I'm like the lead guy in a race team's pit crew. I'll design the car, build the car, tune the car, test the car, fix it when it breaks... but it's somebody else who
races the car, not me. (Unless it's a server.
)
There's two separate worlds here: Systems & Desktop. Each have very different end-goals despite the fact they share many intermediate goals along the way
I think any impatience you feel is more the result of what your real job is. If your real job is the technology itself (systems), you're more likely to put up with dumb-ass design decisions because it's...well...it's your job to do that. If your real job is to get results
out of a piece of technology (desktop), then anything that gets in the way of speedy results is an annoyance at best.
Two different worlds. And each correct in its own way.
