I really wish someone would start to make enterprise software well documented.
Most of the stuff I have to deal with has a truckload of marketing bullcrap and very little sane technical documentation with a total lack of community. Also most of the stuff is very unflexible, outdated and slower than a snail.
I can go on all day, there is no end to the weirdness of "enterprise" software. It's really bad.
I would not be so sure at that. I see plenty of people doing that.
It's mostly habit, I think. Even somewhat technically versed people do that (many of them who have been working with computers for more than 15 years).
The most dominant reason for me not to sign up to most random services is that I'd have to manage another set of credentials. There are tools for that, but it's still a hassle (and I value my time). Just use SSO solutions like clickpass (I'm in no way affiliated, just the first thing that came to mind), and I might stick around, if I like what you provide.
No, but I just generate a token for each user and send it to their email when they request it (an account is created if that address doesn't exist). There's a URL that accepts the token and logs them in, that's pretty much it. Hardly anything to open-source.
Even worse, as the article mentions, is having another set of credentials that you can't ever delete. I don't want hundreds of different websites all with an account for me that I'm not ever going to use.
Totally reasonable. And as a social networking Luddite, I also appreciate you being hesitant to cut me out of your pool of potential customers in punishment for the offense of not already being a customer of an unrelated company.
But in turn, I might be reluctant to trust you with my credit card numbers. And to be honest I do get sick of having to come up with more un/pw combinations to remember.
What I'd really like to see more of is using OpenID for third-party authentication, and also some third party (I hate to say PayPal, but. . . PayPal) for financial transactions. Because it does save both of us from having to navigate that whole quagmire of trust & authentication yet again.
1. You'd certainly have to choose the right sources for SSO. I'd say people usually trust their Google account, so that's a good start (and Google does payments, so they make sure to keep it tight). Then go from there, I'm sure other dominant platforms have similar offerings.
2. You can provide an alternative set of credentials. HN is an excellent example. You can log in via id+password, OpenID or clickpass.
3. I will resist signing on until I know you (your application) better. It is more effective to get my attention first (with something like a limited intro, showing what's it about) and once I get hooked, present the payment options. Putting up a pay wall before showing anything is putting me off. Start with light authentication and then add to it once money enters the game.
ps. Requiring users to create new credentials also results in the "one password for everything" phenomenon that's so prevalent. I very much doubt that that will increase security. I'm more inclined to believe that it will do the opposite, as your service will most likely get the less secure/shared password from the get go (remember, you customers don't know how much they will value you later on).
Adding to that, "just organizing it" has one substantial problem: people generally disagree in how to organize the world and what they see as priorities (stuff they want to find), so any one way to do this would be the wrong one for the big majority.
It did cost a lot, but honestly, as a programmer I type so much, its totally worth investing in a good keyboard and I love my DAS keyboard.
The only thing I wish is that the keys were in a flat grid rather than staggered, but it seems very very hard to find any keyboard like that, so no biggy. I've considered getting a Kinesis for years now too, but since I got the DAS, I've had no plans of switching any time soon.
I haven't completely worked out my vim bindings since I've been doing a lot of Qt development in QtCreator lately and just used that without vi mode. I use Colemak for my layout so some of the default keys are a little less than optimal, but I also don't want to change them too much. With one or two simple key swaps it seems quite usable though.
On windows (where I don't use vim) I did map alt-gr to some common programmer symbols; mapped caps lock to control and control to backspace. On my laptop I use vanilla colemak though (including caps lock as backspace, though I'm likely going to change that some time).