RE: October 12, 2005

As usual, Joel nails this one…

“Custom development is that murky world where a customer tells you what to build, and you say, ‘are you sure?’ and they say yes, and you make an absolutely beautiful spec, and say, ‘is this what you want?’ and they say yes, and you make them sign the spec in indelible ink, nay, blood, and they do, and then you build that thing they signed off on, promptly, precisely and exactly, and they see it and they are horrified and shocked, and you spend the rest of the week reading up on whether your E&O insurance is going to cover the legal fees for the lawsuit you’ve gotten yourself into or merely the settlement cost. Or, if you’re really lucky, the customer will smile wanly and put your code in a drawer and never use it again and never call you back.”

Set Your Priorities

[Via Joel on Software]

RE: Why do login dialogs have a "User" field?

I like Jeff Atwood’s blog, but I don’t agree with his posting about removing the “User” field from the dialog box. If you pull the user out of the user/password combination, you have to force unique passwords in your system. That’s a huge hurdle. I know couples where they share the same password for their individual email accounts. Technically, that’s less secure than different passwords for each others account, but it’s easier to manage.

Another problem is that two people could have unique passwords that only differ by a single charactor. If you mistype your password when you login and your password matches the password of another user, then you will login as that user without any warning.

In The Humane Interface, the late Jef Raskin asks an intriguing question: why do login dialogs have a “User” field?

Shouldn’t login dialogs look more like this?

Login dialog without user field

And you know what? He’s right. Your password alone should be enough information for the computer to know who you are.

Click here for the rest of that article

[Via Coding Horror]