> 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 your team come off as combative, thin skinned and hostile to outsiders. But, you do you bro.
From this example the same feeling would be generated by someone else internally already working on the same idea without needing any prompting from anyone in the actual meeting. This can actually be quite common in games where people will give a lot of unsolicited design ideas as feedback or part of bug reports. There's going to be collisions there without anyone's ideas being copied or stolen without credit.
That is "combative, thin-skinned and hostile to outsiders"?
They say they caused it. They explain the cultural attitude that led to it. They plainly state they were wrong.
The "We get it, Microsoft sucks, we should all be fired, rah rah" is responding to the typical outraged rants from immature people who think it's cool to leverage extreme levels of criticism at people and teams who work in large corporations.
Yes. They reference an apology, didn't actually make one, and it was roughly a year after they were combative, thin skinned, and hostile to outsiders. So their words now don't negate the fact that they were actually those things.
And the original now-edited response here was itself still combative, so I don't have much reason to believe they've actually changed rather than just trying to put a nice public face on about it.
There’s too many fluffy words in that.
“We were dicks to the person (people) that pointed out a better way. We didn’t truly investigate the proposed solution at first, we acted combative,
and we were wrong.
We’ve now implemented the proposed solution in an experimental renderer that you can all use and we’ll try to do better from now.”
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
Casey is also responding to unprofessionalism initiated by MS. (Though admittedly the "they started it" defense isn't a great one)
I don't get where the big issue is, a guy smugly makes a suggestion, the devs argue with it and point out that his tone isn't helping. The guy turns out to be right, the devs implement his suggestion. They don't have a history of thanking people by name so they make a vague attribution. Guy continues to be hostile against them, dev calls him out and now he's the asshole? Come on.
That's... Not better?
EDIT: Actually, I thought of a way for that to be better, but it still doesn't make anything better here. If MS is used to working with b2b, where a customer comes in with a bug and MS fixes it and pushes the fix out, there it could be reasonable to not give credit; I don't condone it but it does match the culture there. The problem is that this very much does not translate to FOSS and/or public collaboration with individuals, where there very much is a culture of sharing credit.
Welcome to Microsoft!
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.
1. Know what you did wrong: > When confronted with being told our rendering pipeline had terrible performance, we turned inward. [...] We were wrong.
2. Keep it simple, being careful not to start up a fight, a disagreement, or open up the situation for further discussion or recriminations. Subjective. You decide.
3. Be prepared to meet resistance. They are here meeting their resistance.
4. ...I hope you will accept my apology. > we hope that you will accept our apology
5. Be polite. Subjective. You decide.
6. Remind the person of all the fun times that the two of you had together. > experience we can all learn from to not only improve ourselves
7. Try not to smile. It's text. Sure.
8. In some situations a small gift may serve as a token of apology. > As such, we dedicate this experimental renderer to the community as an olive branch.
9. Express yourself. > a capability and willingness to learn from our past mistakes.
10, 11 remain to be seen.
This is a good exhibit of an almost perfect apology. If you've been okay hearing "sorry" your entire life then I am afraid you've been lied to more often than not.
If you specifically focus insults on an individual and call into question their competence and then make a vague statement that avoids actually saying you did something wrong ("We turned inwards), you have failed to do #1, which is arguably the most important step.
It was an awful attempt at an apology that could easily pass for something written by a politician. Directness is a virtue when it comes to apologies.
Counting check marked boxes on a wikihow list isn't a good way to measure the quality of an apology.
> Counting check marked boxes on a wikihow list isn't a good way to measure the quality of an apology.
If anything, it's a way. Suggest something better for your definition of "good", as it looks like you're making a speculative criticism for your own edification.
I already mentioned two things that would make it a "good" apology:
- Directly mentioning whom you are apologizing too. In some cases addressing a group might be appropriate but in this case it seems like he should have mentioned Casey.
- Directly mentioning what you did wrong instead of phrasing it in an intentionally vague way like "we turned inwards".
Apologies are simple in composition. The hard part is getting over our egos.
In this scenario it really isn't Microsoft who are demonstrating a bleeding ego.
Whatever you think about the apology, Microsoft made it without being called to do so. As an inconvenient data point, the apology (again, whatever you think about it) was omitted from the tweet. Casey blatantly rephrases the employee's words from "could be seen as impugning the reader" to "you are impugning the reader". This is all p-hacking convenient facts into one specific world view, and the fanbase is all too eager to echo it.
All of this drama is great for one specific ego.
My bad that part of the comment wasn't directed at Microsoft, its just something that everyone in general has to face when apologizing.
I do agree that Casey should have linked the apology blog regardless of whether he felt it was sufficient.
They don't even mention the person. Pretty hard to argue they covered this.
I assume WikiHow thought it was too obvious that you had to actually send it to / mention the person you were actually apologising to.
Seems pretty sincere and decent to me.
Its like an email that says “attached”, but there’s no attachment.
I'd rate it 4 out of 10 on the NOTSORS scale [1]
[1] No Apology to Sincere Apology Rating Scale™
And I wouldn't even be so hard about them if their initial now-edited reply in this thread wasn't also combative & demeaning.
If stuff got that personal, then I’m not shocked that an impersonal apology was not accepted. If I were to apologize in a situation like this, I’d probably have started by talking to Casey directly about the whole thing before posting in public.
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 less. but people being weirdly pedantic about which words do and do not constitute an apology just because the source is Evil Microsoft Guy.
That is 100% an apology
In this case, the comment from an MS employee in this thread indicates a potential lack of sincerity. If not for that I'd probably give more benefit of the doubt.
> We were wrong. As such, we dedicate this experimental renderer to the community as an olive branch. 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.
Seems rather childish.
There is a "we hope you (the community) accept the apology" - which apology ?! there wasn't one to begin with, because there is no "I/We apologize/are sorry" in the first place.
And the apology should go to the individual harmed, not to the "community"
The apology focuses more on what they did wrong internally, without getting into enough specifics of how it affected the external parties. And, some very serious issues weren't even mentioned.
Then they come out and blame Casey for "not accepting the apology".
So in fact if they can't own the mistake, issue a direct apology, and act like adults, perhaps it's better to let the corpo PR speak in bland tones.
EDIT: the GP of this thread edited their post:
> Casey, I'm sorry. We made a mistake. I made a mistake!
Now, this is an apology.
Also, good apologies come with admission of fault and steps you'll take to make sure you don't make the same mistake again.
> We were wrong. As such, we dedicate this experimental renderer to the community as an olive branch. 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.
This response shows how little you value users feedback (and how unafraid of them you are). Probably should leave this kind of thing to your developer relations team...
It's only an apology in the manner of soulless corporate jargon then. A generic statement following a personal/directed insult does not count as an apology.
Edit: also the following
> (Note: I've iteratively edited this post, as it was originally a one-sentence diatribe written in anger. I originally asked, "I just don't know what else he's asking for here. Credit? Us to die screaming?" It was not a good look.)
I think your comment and it's different iterations demonstrated very well how you guys (still) feel about this.
People should learn to express themselves professionally and keep up the standards, on the professional communities, this is not /b/
> Casey rightly did not acknowledge it except to tell his followers that it was not a real apology
> Casey, I'm sorry. We made a mistake. I made a mistake! We didn't know what we didn't know, and thought we were clever enough to pass for it.
Your edited post starts of with the feeling that you are pissed at Casey, they are dunking on your team yet again. Then you go on to apologize to them.
Jesus fucking crist mate, no post would have been better than this.
Well, it wasn't a real apology. It was "We hope you accept our apology
When you apologize, you say "I am sorry [insert other words of explantion]." Then you can say "We hope..."
What you did simply refers back to an apology that wasn't actually made. Considering that he was correct in saying the problem was simple, his tone was not actually combative, it accurately characterized the problem. So you belittled him & insulted him, and as you admitted you then failed to give credit where due to him & others. He has a career as well. Wouldn't it be nice for him to be able to pad his Vitae with a win on something like this?
Then your initial response he was, as you said, "not a good look". The edited post is better, but still not very good.
Man, you have to take criticism better than that. Remember, we don't know anything about this other than the tweets plus these replies from you and your colleague here on HN. So the tweets honestly didn't seem to describe a particularly bad problem, the only thing that stood out to me was the fake-name-on-discord thing which is yet to be substantiated. I was willing to chalk it all up to an OSS contributor feeling ignored and ranting a little, but the feeling I have now is that there's some pettiness and bickering going both ways.
The idea that vaguely saying sorry to an abstract community should resolve this entire issue is repulsive. Merely stating an apology does not thereby grant you forgiveness.
I had a neighbor who once tore up my yard doing construction. They apologized profusely, but outside of words never made any meaningful recompense. If I complain about the damage am I in the wrong simply because he utter some words of apology?
The tone here sounds like you're more annoyed that Casey was right and wish you could go back to feeling clever.
Writing an "apology" for taking credit for someone else's work, without naming the person who did the work, is just adding insult to injury. Actually making amends would involve giving credit, both in your apology and by adding their name to the top of the original announcement if you can still edit it.
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.
The way to navigate the conversation would have been something closer to this: "I thought it was already doing this, but I'll check again, maybe we misread the doc. Also there's X, Y, and Z to consider that may make what you suggest harder than it seems on the surface".
That all being said, I kind of don't like anybody in this kerfluffle. I think your assessment of his character isn't terribly off the mark and now you're caught in a version of "the worst person you know actually has a point".
Now, we can sit here and discuss whether his approach engendered a response in kind or not, but at some point, someone has to be the duck and let the personal slide off their backs.
unfortunately, ego is what prevents this in a lot of people. Their self-worth is linked to being correct, and people pointing out that their foundational beliefs are wrong cannot be acknowledged.
Translation: While I'm ostensibly apologizing please note that I'm actually the victim here, everyone please feel sorry for me and my team.
One is forced to wonder how, in an entire team working on a terminal emulator, no one thought to use the texture atlas. I mean, that's basically how the actual physical terminals the software is emulating worked in the first place. Then, when told about the obvious implementation, the reaction was not to slap one's forehead and say "Of course, it was so obvious!", but instead to tell a decades-experience game engine developer that they didn't understand how rendering works.
Mind boggling.
It's not a crime to be naive, but lashing out in response is a problem, as we've seen.
- You insisted this was a "doctoral research" (your words) and that he was "misguided" (Leonard's words)
- When it turned out he was right, you posted a non-apology (you didn't even name the person you were apologizing to)
- A year later Leonard who claimed it was so hard now writes a blog post that "solution is trivial" and was "suggested by a community member". Once again failing to acknowledge the person who gave you this trivial solution
What more you could've done? What do you think?
And Casey didn't? Please take into consideration that Casey's definition of the solution as "simple" can sound quite insulting as well.
If someone stated that something is "simple" with an overtone of "are you blind", instead of showing more humility, I would feel insulted too.
It can sound insulting only to people who originally claimed that what Casey suggested requires "doctoral level research into performance". Only to then implement exactly what he suggested.
> If someone stated that something is "simple" with an overtone of "are you blind", instead of showing more humility
Please re-read the original GitHub issue from the start: https://github.com/microsoft/terminal/issues/10362
He is there trying to understand an issue, providing suggestions etc. And generally being baffled how a modern terminal on a modern machine can output text at something like 5 frames per second.
After that Windows Terminal team barges in with "what you’re doing is describing something that might be considered an entire doctoral research project in performant terminal emulation" to... only do exactly that later.
And what Casey said was going to be simple is this: https://github.com/microsoft/terminal/issues/10362#issuecomm...
Tell me how this is insulting to anyone except the people who now claim that "oh we'd been aware about this approach before Casey opened the issue"?
Good question why insult him for his use if you feel its appropriate language?
> As the message evolved, that became more and more out-of-place.
The wording didn't "became more" it was inappropriate from the start and instead of acknowledging this you and lhecker have tried walking back every excuse to downplay this. You both don't think it was out of place or inappropriate you are both just upset that you got called out on it.
1. I'm sorry 2. It was my fault 3. How do I make it right?
You have to scroll down a bit. Whether that's an apology or just "please accept our apology that isn't actually here," is debatable. An actual "We were wrong, we're sorry" would have been clearer.
What more really needs to be said? Feels like one of those times where if everyone just sat around at a pub with a beer, everything would be resolved. Instead it's just little snide remarks back and forth. It's a shame, I really like Casey, and he was definitely right, but it's probably time to move on.
An actual apology. Jesus Christ, has no one at Microsoft ever apologized to a human being? I mean apologized, not passive-aggressively, condescendingly issued a generic apology line in the P.S. to an email on a completely different topic? It goes like this: heeeey, Casey, we're really sorry about <whatever we did> and we would like to apologize. We understand we were wrong to do it because <reasons>. This is not how we want to treat people and the fact that we let it happen was a mistake. I'm sorry we went through this but <here's what we plan to do so that we don't make the same mistake again with someone else>.
That is an apology. Once you say that, you're entitled to asking the community at large to accept it. But you can't say "please accept our apology" without issuing a damn apology. That's like saying "please accept our complimentary cake" without sending any cake!
I realize basic human decency may be a faux pas in large corporate settings but doesn't Microsoft employ at least one PR person who understands PR 101?
I tell my kids this all the time. An apology has several parts:
1. In clear terms, admit fault. "I responded to a comment with some vitriol, and at the time that seemed okay but looking back that was insulting and rude, and not how I want to address our community members. This is true in any case, but doubly so when the original commenter turns out to have provided good advice that I was ignoring." 2. Express remorse. "I'm sorry. I regret letting my passions get the better of me and hope I didn't damage any relationships." 3. Offer to remediate. "As you can see, we're embarking on doing exactly the work that $AUTHOR suggested, and I'd like make sure they receive appropriate credit. If it helps, I'll link to the original thread and this apology." 3. Do better.
The quotes above are just examples off the top, I have no horse in this particular race, but I do have a lot of experience eating crow and having to apologize for being an ass to someone who later turned out to be right.
Well if I were to write an apology "frankly to <person>" I would probably mention <person> by name in the apology.
ASK HIM
We've created the most incredible communication platform in human history and no one actually talks to each other, everyone just tries to publicly snipe.
This week's blog post refers to them as a "community member" [of Microsoft]. Such a self aggrandizing term.
Someone reported a bug on github. Your team dismissed them and peppered them with deflective words to pretend that the team is making a safe space for employees that don't care at all.
Your edits are getting closer.
Unironically, yes, UNLESS...
- You're willing to take a serious look in the mirror (and understand that the way you reacted to the situation was defensive, passive aggressive and inflammatory rather than direct, constructive and conciliatory)
- You assign credit where credit is due
- You do a good faith post-mortem and come up with some way to make sure this won't happen in the future
Now, if that happens, then obviously you should not be fired; if anything, you should be rewarded as handling difficult situations like this correctly tends to be the true test of one's capabilities as a professional. Unfortunately, it's high stakes, high rewards -- which also means high risks and consequences.
It's not easy to say "We made a mistake. Not only that, but there's no easy 1-shot fix to undo what went wrong. Let's sit down together and discuss, and we'll listen. Then, we'll go and think about that for a while and come back to you with where we align, where we differ; and so far as where we agree, where we think we can improve. What do you say?"
It may not be easy, but it's worth it.
Relationships are built in the muck.
Good question why insult him for his use if you feel its appropriate language?
No, Microsoft doesn't suck. It's a great company. It's some people there that suck, and one just got self-identified.
https://news.ycombinator.com/newsguidelines.html
> Throwaway accounts are ok for sensitive information, but please don't create accounts routinely. HN is a community—users should have an identity that others can relate to.
So you stole his idea and realized a one-liner dismissal was not a "good look" for yourself, so you wrote an "apology"? It's not about him, it's about saving yourself from the blowback. This and the events documented are the closest thing to a psychopathic programmer I've ever seen.
English is indeed not my first language, but I've lived in North America for 25 years and stakeholder communication is part of my job description. "I did something wrong; please accept my apologies" to me is boiler-plate standard, sufficient, acceptable way.
Your blog post goes way past that! It says "We caused the kerfuffle". Even "We were Wrong", explicitly! I for one understand your frustration and probably real question of "What else do you want from us - keel over and die?" - it's just that humanity is not an acceptable feature to show from people HN wants to hate on already.
That's OK though. Their reaction here will simply mean we'll get less sincere humane posts like yours, and more corporate-sanitized meaningless PR, which I'm sure will make those very same people much happier. And yes that's a pointed /s :-)
The apology is written almost tactically to avoid dealing with specifics. When the OP additionally started this entire thread with anger, the idea that steps have been taken forward is pretty much dead.
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 apology[2].
This blog post is matter-of-fact, but Casey is right. However, he said himself that it was trivial to do this. Is it not acceptable that we use the same language?
Casey, I'm sorry. We made a mistake. I made a mistake! We didn't know what we didn't know, and thought we were clever enough to pass for it.
Using a texture atlas was a great idea, and we didn't know about it until you told us. We should do better to credit you.
[1]: https://devblogs.microsoft.com/commandline/windows-terminal-... (scroll down under the image)
[2]: https://twitter.com/cmuratori/status/1489406091318349826
--
(Note: I've iteratively edited this post, as it was originally a one-sentence diatribe written in anger. I originally asked, "I just don't know what else he's asking for here. Credit? Us to die screaming?" It was not a good look. It also originally contained "I get it, Microsoft sucks, we should all be fired, rah rah rah." As the message evolved, that became more and more out-of-place.)