We have a system for logging issues (error, mistakes, problems we've encountered). One day, Phil was talking with someone about some procedure. He says, "wow, this is a pain". Phil encourages him to put this in the issue log. He hesitates, not wanting to bother.
Phil considered putting an entry in the log regarding his colleague's inability to log issues.
Sunday, May 27, 2007
Tuesday, May 1, 2007
Sensitive Information
We got a message about sending sensitive information in an email. I won't quote the email (since that might be sensitive) but the excerpt is:
Subject: Emails vs face to face communication
[...]
When a sensitive business issue comes up [...] go and talk to the person(s) that
you might have otherwise emailed. [...]
I am happy to answer questions -- face to face if they are sensitive!
The $32,000 question is: if this email is sensitive (to the point of me not being able to quote it here), shouldn't the author of this email have talked to us about it instead of emailing us?
Subject: Emails vs face to face communication
[...]
When a sensitive business issue comes up [...] go and talk to the person(s) that
you might have otherwise emailed. [...]
I am happy to answer questions -- face to face if they are sensitive!
The $32,000 question is: if this email is sensitive (to the point of me not being able to quote it here), shouldn't the author of this email have talked to us about it instead of emailing us?
More emailmeta
From: Phillip Wei
To: Colleague 2
CC: Lukasz Strozek
Subject: RE: SQL Standards
> I don’t think enforcing rules is necessary
As a rule, neither do I.
From: Colleague 2
To: Colleague 1; Phillip Wei
Subject: RE: SQL Standards
Colleague 2: There are no company-wide standards. I don’t think enforcing rules is necessary, but common convention is
...
(defines some naming scheme)
From: Colleague 1
To: Colleague 2; Phillip Wei
Subject: SQL Standards
Are their any naming standards for adding constraints on a table?
To: Colleague 2
CC: Lukasz Strozek
Subject: RE: SQL Standards
> I don’t think enforcing rules is necessary
As a rule, neither do I.
From: Colleague 2
To: Colleague 1; Phillip Wei
Subject: RE: SQL Standards
Colleague 2: There are no company-wide standards. I don’t think enforcing rules is necessary, but common convention is
...
(defines some naming scheme)
From: Colleague 1
To: Colleague 2; Phillip Wei
Subject: SQL Standards
Are their any naming standards for adding constraints on a table?
Contronyms
http://organizationsandmarkets.com/2007/04/23/contronymns/
It would be great if contronyms were also words which were not their own antonyms.
Phil didn't get it.
It would be great if contronyms were also words which were not their own antonyms.
Phil didn't get it.
Emailmeta
(don't confuse with metaemail).
It has become customary for me to paste an excerpt from an email chain Phil, Nick and I were having at work. This is a good part of metayada -- it shouldn't be the only thing I do, but it helps keep the meta going!
P.S. This one below serves a double purpose -- the original message contains a link to a piracy case. Definitely check it out!
P.P.S. It was challenging to write it up -- I had to escape all the brackets and ampersands like this:
<NoCloseTag>
<Tag Value ="&lt;Amazed Quantifier='Speechlessly'/&gt;">
(you get the joke)
From: Lukasz Strozek
To: Nicholas Elprin; Phillip Wei
Subject: RE: wow
<NoCloseTag>
<Tag Value ="<Amazed Quantifier='Speechlessly'/>">
unless that was deliberate? i don’t know anymore?
From: Nicholas Elprin
To: Lukasz Strozek; Phillip Wei
Subject: RE: wow
<NoCloseTag>
<Tag Value =">Amazed Quantifier='Speechlessly'/<">
From: Lukasz Strozek
To: Nicholas Elprin; Phillip Wei
Subject: RE: wow
<NoCloseTag>
<Amazed Quantifier=”Speechlessly”/>
From: Nicholas Elprin
To: Phillip Wei; Lukasz Strozek
Subject: RE: wow
that's invalid. i think you mean:
< NoCloseTag >
<speechlessly amazed />
From: Phillip Wei
To: Lukasz Strozek; Nicholas Elprin
Subject: RE: wow
<speechlessly amazed>
(no close tag)
...
From: Lukasz Strozek
To: Nicholas Elprin; Phillip Wei
Subject: wow
http://arstechnica.com/news.ars/post/20070430-consultant-antipiracy-group-pirated-my-data.html
It has become customary for me to paste an excerpt from an email chain Phil, Nick and I were having at work. This is a good part of metayada -- it shouldn't be the only thing I do, but it helps keep the meta going!
P.S. This one below serves a double purpose -- the original message contains a link to a piracy case. Definitely check it out!
P.P.S. It was challenging to write it up -- I had to escape all the brackets and ampersands like this:
<NoCloseTag>
<Tag Value ="&lt;Amazed Quantifier='Speechlessly'/&gt;">
(you get the joke)
From: Lukasz Strozek
To: Nicholas Elprin; Phillip Wei
Subject: RE: wow
<NoCloseTag>
<Tag Value ="<Amazed Quantifier='Speechlessly'/>">
unless that was deliberate? i don’t know anymore?
From: Nicholas Elprin
To: Lukasz Strozek; Phillip Wei
Subject: RE: wow
<NoCloseTag>
<Tag Value =">Amazed Quantifier='Speechlessly'/<">
From: Lukasz Strozek
To: Nicholas Elprin; Phillip Wei
Subject: RE: wow
<NoCloseTag>
<Amazed Quantifier=”Speechlessly”/>
From: Nicholas Elprin
To: Phillip Wei; Lukasz Strozek
Subject: RE: wow
that's invalid. i think you mean:
< NoCloseTag >
<speechlessly amazed />
From: Phillip Wei
To: Lukasz Strozek; Nicholas Elprin
Subject: RE: wow
<speechlessly amazed>
(no close tag)
...
From: Lukasz Strozek
To: Nicholas Elprin; Phillip Wei
Subject: wow
http://arstechnica.com/news.ars/post/20070430-consultant-antipiracy-group-pirated-my-data.html
Subscribe to:
Comments (Atom)