Earlier quoted context omitted.
> I also probably would not have responded favorably to that wording – irrespective of if they were correct. Why not? I see nothing wrong with this sort of feedback. It's blunt, but constructive.
If it was your code they were talking about, you may feel differently. Blunt, hyperbolic statements like "massively overcomplicated" can feel like a shot across the bow when someone is talking about code you wrote. Kindness and gentleness go a long way in OSS.
When I tell the Windows Terminal team something is simple, I am "misguided"
71–80 of 476 posts
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#72Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#73Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
1. I'm sorry 2. It was my fault 3. How do I make it right?
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#74[1] https://twitter.com/cmuratori/status/1522471966929653761
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#75Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
Someone is upset and venting. This comment comes across to me as "Ugh we already said the right words. Their distress is so inconvenient to me, why isn't it stopping?"
EDIT: Typically in this community we denote when a comment has been edited to change a critical piece of the message...
I'm detecting very little genuine authentic empathy
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#76Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#77Earlier quoted context omitted.
> except to note that it was not an apology at all. Ctrl-F there doesn't show a single "sorry" in the text. Or "Casey" for that matter. Why is it so difficult to say: "Casey, we are sorry, you were right and we were mistaken.". Instead there is a nebulous ~extended a branch to community and hope to accept our apology~ (paraphrasing) without offering an apology in the first place.
try looking for the word "apology" edit: > We know we have so much more to learn, but we hope that you will accept our apology and understand we’re humans behind this product with a capability and willingness to learn from our past mistakes. If someone said that to me, I would say "oh ok, no problem dude" and move on with my life. Not even defending the microsoft guy, I have zero skin in the game and couldn't care le…
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#78Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
I’m kind of in awe by the unprofessionalism of this response. In an era of incessant corporate PR, it’s somewhat refreshing lol.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#79Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#80Another day, another Casey post dunking on my team. Hi! This tweet misses the mark only a little bit; in a previous blog post, we apologized[1] pretty frankly to everyone involved in this discussion. I'll admit that we didn't list him by name, but neither did we list the other handful of folks involved. We should have. In turn, Casey rightly did not acknowledge it except to tell his followers that it was not a real a…
This kind of tone really doesn't engender sympathy: > We get it, Microsoft sucks, we should all be fired, rah rah rah. > I just don't know what else he's asking for here. Credit? Us to die screaming? The blog post is matter-of-fact, and Casey is right: however, he said himself that it was trivial to do this. Is it not acceptable that we use the same language? Your "apology" really is anything but. If anything you and…