>>>>> "David" == David Parter <dpar...@cs.wisc.edu> writes:
>> I personally think this scales down to even a small company. And >> please, let's get away from those asinine first.last@ email >> addresses. They just don't scale. But god knows why some CEOs >> continue to insist on them, like my current job. Stupid. David> I love naming conventions that include "except when they don't" David> -- since there will *always* be exceptions, I'd much rather David> that everyone knows that there is NO naming convention, and if David> they don't know LOOK IT UP -- don't assume. Yeah, at the previous company to Lucent, the standard was "two or three initials of person's name"@.... which also sucked when you had lots of people with J. S. for their two initials. One person got 'js', another got 'jfs' (me!), another got 'jxs' because they didn't have a middle initial like the first one... So any stardard is going to break no matter what you do. Which is why I liked the Lucent one. There was no standard name, which meant no standard expecations to break. My current company's standard is 'first five characters of last name, followed by first initial', with exceptions handled on per-user basis. It still sucks in alot of ways, because I hate being 'stoffj'. :] Oh yeah, outgoing email from work is re-written to first.last@ though internally it's not. Sorta. Depends on what Notes is feeling like that day. 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/
