3 ms·
Also, when you send an email, the content is instantly dead. You can't correct it, you can't edit it, and you can't improve upon it. Generally, when you send a
by jimfl 17y ago
Also, when you send an email, the content is instantly dead. You can't correct it, you can't edit it, and you can't improve upon it.
Generally, when you send an email, there is some context, many times also electronic, and the mail is disconnected from that context. The content of collaboration should be close to what is being collaborated upon, and tools for work (i.e. IDEs, SCMS) should be designed to support collaborative communication.
- JimmyL 17y agoThat's often the point - to provide an immutable record of a conversation or of the passing (or not passing) of a message. As much as this is against the spirit of an agile workplace, the "deadness" of an email (and the external time stamping) is a critical part of most people's corporate CYA routines. I work in a moderately-progressive workplace, and if I ever need to seek the input of a supervisor on a big issue/something that may come back to haunt me, I'll talk to them about it, and then send them an email saying what we decided. This makes it clear what the decisions was (and more importantly, how I interpret it) and provides documentation to both sides that the issue was discussed and a conclusion reached.