3 ms·
IMO, In this particular case, face-to-face discussions will make the matter worse. The co-founder doesn't READ his emails/IMs let alone remembering what has be
by AjJi 16y ago
IMO, In this particular case, face-to-face discussions will make the matter worse.
The co-founder doesn't READ his emails/IMs let alone remembering what has been discussed.
- JabavuAdams 16y agoNewsflash. Nobody reads (I mean really reads) e-mails. Get used to it.
- AjJi 16y agoAre you saying that I was doing it the wrong way the whole time? :D I mean, you really can't make that a rule. I read (and re-read) important mails, I guess I'm not the only one, am I ?
- owkaye 16y agoOf course you're not the only one who reads his emails. JabavuAdams is FOS as far as I'm concerned. I've been a developer for almost two decades and I always read my emails -- CAREFULLY. In fact I have every client agree with me from the beginning that our emails serve as the written terms our agreements when we both agree in writing. And I ask them to always save every email they send me and every email they receive from me, so that we will both have a written trail of correspondence to refer to when (not if) there are any misunderstandings. This system has served me well for many many years, so for someone to make an all-encompassing claim that no one reads emails is just plain ridiculous.
- JabavuAdams 16y agoCome on, do you seriously believe that I'm arguing that 0 people read e-mails? What I was trying to convey is that you'll constantly be surprised at the number of intelligent, educated, detail-oriented people who did not in fact read what you wrote. If you optimize your communications to assume this, you will become a better communicator. EDIT> There's another important subtext here. I've often seen the following pattern: developer is confronted with user behaviour, but continues to talk about "I do this, I do that", rather than internalizing that others do not do as he does.