Coda was obviously not thrilled that @jodastephen apparently (from updates written at the top of his post) decided to
(1) widely publish personal correspondence that wasn't meant to be sent to him,
(2) mirrored it when Coda removed his copy from the net,
(3) insinuated it was a public statement by yammer, whereas it was private thoughts from Coda, and
(4) wasn't even classy enough to contact Coda before publishing it.
Maybe I'm particularly sensitive to (3) because an jerk on HN insinuated that my posts here were representative of the company I worked at, but none of those four things are particularly nice on @jodastephen's part. Note also that, depending on your employer, (3) can get you in quite a bit of trouble. @jodastephen claims he found the email on HN or twitter, but that doesn't mean he has to repost it. Just like when you see accidental tits photos sent from someone's phone, you can either close the tab or repost it to spread it to the world.
That said, it's obviously interesting that the build situation for larger projects seems to be a shitshow, but still, an email to Coda before posting wouldn't have hurt.
The context also matters -- as Coda mentioned, this email was only in regards to the negatives with scala and doesn't mention any of the positives.
I understand and agree with everything you said. Coda has every right to be angry with Stephen. He might even have the right to sue Stephen. Nonetheless, swearing in public like that was simply not the way to deal with the situation. Think about it in purely strategic terms. What outcome might Coda or Yammer want from this? Perhaps for it to fade away, perhaps for Stephen to apologize, perhaps something else. Does snarling at Stephen bring any of those outcomes closer? Did the swipe at HN? If Stephen or anybody else - I suppose some might think that includes me - harbored any ill will, wouldn't this just give them even more opportunity to do some damage?
Sometimes the right thing to do when you're wronged is to let it pass, no matter how much it sticks in your craw, for strategic reasons. Sometimes giving in to that moral-outrage addiction simply does more harm than good, no matter how justified the outrage might be. And yes, I've very much been in that position myself. It sucks, but I've learned that it sucks even more to have a self-inflicted wound on top of the one I got from someone else.
(1) widely publish personal correspondence that wasn't meant to be sent to him,
(2) mirrored it when Coda removed his copy from the net,
(3) insinuated it was a public statement by yammer, whereas it was private thoughts from Coda, and
(4) wasn't even classy enough to contact Coda before publishing it.
Maybe I'm particularly sensitive to (3) because an jerk on HN insinuated that my posts here were representative of the company I worked at, but none of those four things are particularly nice on @jodastephen's part. Note also that, depending on your employer, (3) can get you in quite a bit of trouble. @jodastephen claims he found the email on HN or twitter, but that doesn't mean he has to repost it. Just like when you see accidental tits photos sent from someone's phone, you can either close the tab or repost it to spread it to the world.
That said, it's obviously interesting that the build situation for larger projects seems to be a shitshow, but still, an email to Coda before posting wouldn't have hurt.
The context also matters -- as Coda mentioned, this email was only in regards to the negatives with scala and doesn't mention any of the positives.