▲ | ChuckMcM 4 days ago | |||||||||||||||||||||||||
I believe this is exactly correct. Email is a 'paper trail' and being able to change that paper trail ex-post facto benefits the sender waaaaaaaaaaay more than it does the receiver. I met an engineer from Google who quit when they insisted on "dogfooding" this. They used the example, you send an email that says lets meet for dinner tonight at 6. You arrive and after 30 minutes begin to wonder, go back to your email and now it says meet "tommorow night" at 6. Are you crazy? Did you misremember? Or did the sender change the email after they sent it and you read it? How could you complain? As I understand it, it was met internally with "that isn't what we mean." But the ability to send HR important announcements and then change them after the fact is a capability that is just too tempting for HR to resist at some point. | ||||||||||||||||||||||||||
▲ | parl_match 4 days ago | parent | next [-] | |||||||||||||||||||||||||
> They used the example, you send an email that says lets meet for dinner tonight at 6. You arrive and after 30 minutes begin to wonder, go back to your email and now it says meet "tommorow night" at 6. Are you crazy? Did you misremember? Or did the sender change the email after they sent it and you read it? How could you complain? This is a calendar invite. And this is a completely valid use case, but it's useless if I don't have an edit log. It's crazy how many people miss that last part. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
▲ | dimensional_dan 4 days ago | parent | prev [-] | |||||||||||||||||||||||||
It's probably going to be even worse than that - HR (and everyone else) will probably then have to implement process and procedure and storage mechanisms to prove that emails have not been changed. This might mean storing emails in a document control system. Email is bad enough but now we're all going to have to keep a mirror in SharePoint or something like that. | ||||||||||||||||||||||||||
|