303 karma · joined December 2, 2012
e.g. having to tell the app things it could just figure out, sloppy focus that requires you to fuss with the UI, having to input a lot of text in small text box that won't resize or spell check it, having to manually click a button to auto-complete, modal dialog boxes that block you from reading important info in another pane, uselessly vague or incorrect error messages for easily correctable problems cause you to waste hours guessing what the real problem is, returns no error message at all, oh you're using the wrong browser, oh to attach a file in your enterprise webmail you need to install Sliverlight, oh the web based wiki plugin for your enterprise document system only works on Windows with IE, oh mobile browsers are not supported, let me slowly redraw the screen a few more times due to some .Net + Areo legacy issue and hang your window manager, supports Kerberos SSO but requires to you enter a password, doesn't let you enter a username or password since it uses Kerberos SSO... etc.
The Sherpa are an ethnic group known for being skilled mountaineers, and it is also a way some of them make a living. It's not like they're a climber helping cast.
When I asked them to allow me to use a key along with my passphrase they said it would confuse their users, and then acknowledge their users aren't going to pick good passwords and would be at risk:
http://discussions.agilebits.com/discussion/comment/25737/#C...
> A master password constructed with diceware of three or four words should be both strong and memorable, but I have to acknowledge that most users aren't going to use diceware to construct a master password. So I suppose that your point stands.
Additionally the argument that "no interface" means you won't be able to troubleshoot something is an overly literal interpretation of the age old concept. As though "no interface" is not just a design ideal, which may not always be possible, but rather a movement to force round pegs into square holes. A more forward thinking point of view would be what innovation can be made in these areas, vs. looking backwards at how things used to work.
https://blogs.vmware.com/console/2012/12/the-pivotal-initiat...
EDIT: Although he's now the Chief Strategy Officer at EMC, so maybe that's good. http://www.emc.com/corporate/emc-at-glance/exec-team/index.h...
http://blog.stephenwolfram.com/2012/03/the-personal-analytic...
2. Choose your language settings, and then click "Next."
Unix had a funny "not a typewriter" error message that eventually ended up in an Apple OS: http://support.apple.com/kb/TA31349
Sounds like a case of Microsoft's user lock-in strategy backfiring. They have had plenty of time to fix their IMAP implementation over the years, but it hasn't been a priority for some reason.
- when creating inky account, typed in my desired login name, it said it was already taken, then changed to ok on its own.
- notes view didn't recognize my notes taken with notepad on an ipad, and tagged with "Notes" in gmail.
- wasn't clear how to enable the different views when you're not in the tutorial.
- email threads don't include my responses, is that intentional?
Some other thoughts: Zimbra had some interesting ideas around deeper inspection of email, like looking up part number in inventory databases if they appeared in the email. They also allowed you to write plugins to parse and do interesting things with the email.