Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Honestly, I think a third way would be good, but sticking with a way would be even better.

A huge, huge chunk of my last year was spent teaching dozens of teachers (long story) who were used to, and very productive with, the '90s way of using files were everything, how all these new cloud things work. The whole thing was extraordinarily confusing. Lots of things that they depended on didn't quite fit with the "let's do away with files" approach, and the fact that they couldn't do it more than compensated for any productivity gains due to easy collaborative editing and the like.

We're all computer nerds here and love to learn new things about computers but most people aren't. People have treated the sick, built the largest buildings in the world, gone to space and developed new vaccines using this clunky, inefficient, Stone Age file-based interface. I'd say it's not too shabby.

Unless a hypothetical third way enables measurable, verifiable improvements (and I mean measurable, not "we asked 10 interns to rate how easy it is to perform these actions", that's an anecdote, not a usability study), that third way would be a net loss for virtually everyone except us.

FWIW: I think the constant UX churn in our industry is just the symptom of an identity crisis. It's what happens when a company (or, as is often the case, an entire industry) is increasingly unable to produce meaningful fundamental improvements, so it's churning visible, but practically inconsequential changes in an effort to justify the money it burns through. In our bubble we all go ooh and aah over the latest UX improvements of whatever piece of software we run into again, but truth is most people just go aww fsck, how the hell do you do X now, over and over again?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: