>> And >> please, let's get away from those asinine first.last@ email >> addresses. They just don't scale.
Edward> I don't get what you're talking about. first.l...@domain is Edward> one of the best things ever. When I meet somebody, I don't Edward> want to remember that they are jsmith, or smithj, or johns, or Edward> johnsmit, etc etc etc... When I'm in a conference with 6 Edward> people from some other company, simply knowing their name is Edward> good enough for me to be able to contact them afterward... I Edward> don't have to know the username policy at their company... Edward> The only time first.last isn't a good idea is when you have Edward> multiple people with the same name. Maybe that's what you're Edward> talking about? Exactly. And it doesn't scale. Even at my small 400-500 person company we have conflicts with names. So, if you have two john.sm...@foo.com, who gets the email? Riddle me that batman... First come, first served? What happens when your new CEO is named John Smith, does email all suddenly switch to the new CEO because he's more important than the programmer who originally had that email? first.last is a crutch which should be taken out back and be buried and forgotten. Thanks, John _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
