3 ms·

I also think saying "we don't bother with documentation or configuration because nobody reads or uses that" is kind of a self-fulfilling prophecy. > Treat peop

I also think saying "we don't bother with documentation or configuration because nobody reads or uses that" is kind of a self-fulfilling prophecy. > Treat people as if they were what they ought to be and you help them to become what they are capable of being. -- Johann Wolfgang von Goethe That always risks being patronizing, but at least we should allow users options and deeper documentation, for those who want to use them -- they shouldn't get punished by being restricted to the lowest common denominator. That doesn't mean there can't be friendly defaults, "wizards", and whatnot.

TeMPOraL 8y ago
> I also think saying "we don't bother with documentation or configuration because nobody reads or uses that" is kind of a self-fulfilling prophecy. Oh yes, and it's so deeply ingrained in the culture. At my previous job, our customer made us use a pretty crappy, proprietary integrated system for task management, bug tracking and version control. Everyone hated it with passion. It took me over a year to finally stop and think for a moment - that maybe it has some more efficient modes of working, and maybe there is some logic to its organization? I clicked Help -> Manual and, lo and behold, I was looking at a large compiled help file describing everything. Every functionality, the fundamental concepts behind the software's UI and data representation. Hell, it even mentioned the API. 30 minutes later, I still didn't like the software, but I was finally somewhat comfortable with it. I was probably the first person to do that in that company. A lesson here is that unfortunately, the instinct to bitch about software instead of trying to find a manual is strong even in power users. I took that lesson to heart, and these days I'm e.g. very friendly with Info pages in my OS. Turns out if software you regularly use has a decent manual, reading it (or at least skimming, and I mean cover to cover) has absurdly high payoff. > they shouldn't get punished by being restricted to the lowest common denominator. That doesn't mean there can't be friendly defaults, "wizards", and whatnot. Exactly. Lower the start of the learning curve, but don't flatten it entirely, don't dumb down your application for the sake of "easy to use". Power always comes with some amount of complexity and learning.

TeMPOraL 8y ago

> I also think saying "we don't bother with documentation or configuration because nobody reads or uses that" is kind of a self-fulfilling prophecy. Oh yes, and it's so deeply ingrained in the culture. At my previous job, our customer made us use a pretty crappy, proprietary integrated system for task management, bug tracking and version control. Everyone hated it with passion. It took me over a year to finally stop and think for a moment - that maybe it has some more efficient modes of working, and maybe there is some logic to its organization? I clicked Help -> Manual and, lo and behold, I was looking at a large compiled help file describing everything. Every functionality, the fundamental concepts behind the software's UI and data representation. Hell, it even mentioned the API. 30 minutes later, I still didn't like the software, but I was finally somewhat comfortable with it. I was probably the first person to do that in that company. A lesson here is that unfortunately, the instinct to bitch about software instead of trying to find a manual is strong even in power users. I took that lesson to heart, and these days I'm e.g. very friendly with Info pages in my OS. Turns out if software you regularly use has a decent manual, reading it (or at least skimming, and I mean cover to cover) has absurdly high payoff. > they shouldn't get punished by being restricted to the lowest common denominator. That doesn't mean there can't be friendly defaults, "wizards", and whatnot. Exactly. Lower the start of the learning curve, but don't flatten it entirely, don't dumb down your application for the sake of "easy to use". Power always comes with some amount of complexity and learning.