Sounds like all three people could do with brushing up on soft skills...
When I tell the Windows Terminal team something is simple, I am "misguided"
121–130 of 476 posts
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#122Another 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…
No post body was provided.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#123Another 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…
For what it's worth, I think it's commendable that you are engaging this externally no matter the tone, instead of the usual cowardly radio silence like most big cos. I find the this-is-not-actually-an-apology nitpicking disappointing; community should be encouraging this kind of conversation, not squashing it.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#124Another 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…
> we apologized[1]
Yeah, that's not an apology. That's something saying you did apologise. It doesn't look like you actually sent an apology, and you never mentioned Casey at all.
If this were a security vulnerability Casey would have gotten a mention (and a Bug Bounty). I guess Microsoft don't care about credit for other stuff.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#125Another 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…
Now can you get Microsoft to fix their broken implementation of FMA? (see https://github.com/MicrosoftDocs/cpp-docs/pull/3526 for details)
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#126Earlier quoted context omitted.
That's a downside of exclusive reliance on written communication, not of remote work. You can avoid this with a phone call or a "can we pair for a bit?" session as well.
I take it "Can we pair for a bit?", means 'meet to discuss..." The non-apology sounded more heartfelt than this.
No, I mean pair programming to work on the issue. More applicable to work colleagues than discussing over github.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#127I really wonder why OSS developers often have so big ego issues. I mean I get it, attribution is nice and all, but trying to force attribution for evey small idea you might have had in your life by trying to rally the public against "the evil corporate enemy"? Really? How low can you sink
There's keeping your head down and silently not giving attribution, and then there's publishing a blog post, boasting how smart you are, and merely mentioning that the idea came from "someone in the community".
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#128Earlier quoted context omitted.
To be fair, the GitHub commenter in question had made this statement: > It really seems like most of the code in the parser/renderer part of the terminal is unnecessary and just slows things down. What this code needs to do is extremely simple and it seems like it has been massively overcomplicated. I think they deserved a better response from Microsoft, but I also probably would not have responded favorably to that…
> 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.
Highlighted portions of Microsoft's response was blunt, but constructive.
> can be read as impugning the reader.
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#129This is worse than it looks, since the person who wrote the blog post is the same person who insulted the dev, and is the same person who joined that dev's related discord under a pseudonym. [1] [1] https://twitter.com/cmuratori/status/1522471966929653761
The fact that he went unmentioned is pretty damning. I don't give Microsoft the benefit of the doubt here -- this reeks of stealing credit under the guise of "open to feedback".
Re: When I tell the Windows Terminal team something is simple, I am "misguided"
#130Another 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…
[deleted]