Warp wrote:
>   When I see someone using the terms, I just can't assume anything (unless
> it can be unambiguously deduced from the context).

Yep. I've been working on trying to make measurements unambiguous in my 
everyday speech and my written docs. For example, your clock is not "ahead" 
of my clock. It's either "showing earlier" or "showing later" than my clock. 
Your colors aren't "brighter" than mine, they're either "more saturated" or 
"lighter hued" or something like that.

(The one that killed me all the f'ing time was when we were selling tickets, 
and the boss refused to distinguish between SKUs and individual tickets. SO 
you never knew if he was talking about (for example) all the tickets to 
Batman need to be able to be refunded, or the individual ticket that Fred 
bought needs to be able to be refunded. Over and over I tried to get him to 
distinguish between the event you're talking about and the individual piece 
of paper that let you into that event, to no avail.)

I've found it's worth the effort, at least when talking to other technical 
people, to be precise and consistent about such things. :-)

-- 
Darren New, San Diego CA, USA (PST)
    C# - a language whose greatest drawback
    is that its best implementation comes
    from a company that doesn't hate Microsoft.

Post a reply to this message