My #1 recommendation on the actual question asked is to get over idol worship and especially caring about what "genius programmers" think and spend that energy on persistence, being a better collaborator, and drilling down until the answers make sense.
-
Show this thread
-
As for the whole terminal tale, I think Casey dropped the ball big time by getting condescending and grandiose, when e.g. Martins had diagnosed several much simpler and smaller-scope in the same thread that seemed eminently-fixable and not politically tricky.
4 replies 4 retweets 99 likesShow this thread -
There was an opportunity to try and get started on that stuff, build rapport, and then later try and get them to work on bigger stuff, but instead it turned first into a shouting match and now some kind of crusade. What a waste of everyone's time.
6 replies 3 retweets 76 likesShow this thread -
Replying to @rygorous
I like how I was condescended to many times in the github thread, over and over, but when I eventually stopped being polite, I am the one who is blamed. It's pretty great.
4 replies 1 retweet 35 likes -
Replying to @cmuratori @rygorous
I don't think this is about blaming anyone. It's just that the way it was handled is not the shortest path to coax the terminal team (or the 1 actual coder there) to prioritize it. The gap was an actual abys (talks abou PhD). Bridging it takes time, Twitter is not the tool.
1 reply 0 retweets 0 likes -
Well separately I would also like it to be acknowledged that this was a customer bug report? I am the one who has paid a lifetime of $200/machine licenses for Windows, and I filed a bug report with a complete benchmark repro case.
2 replies 0 retweets 12 likes -
Why the onus is placed on me to manage the team's emotional state, to be diplomatic, or whatever else is projected on me, is even more frustrating. This was Microsoft _responding to a customer_. It is not like I am on their team, at their company, or am supposed to be friends.
2 replies 1 retweet 18 likes -
Replying to @cmuratori @_karm
I don't think anyone in this thread is saying that you are on the "wrong side" either on the technical level or in the github thread. It's just, if your endgame is to raise awareness for software quality, you do a disservice to yourself by exploding even if you have reason to.
1 reply 0 retweets 0 likes -
If you want to extend your reach you recognize that even programmers are emotion driven machines and "managing emotions" is sadly part of it. It is also perfectly legitimate if you don't want to deal with this. I am not sure I would in your place.
2 replies 0 retweets 0 likes -
Replying to @pasculator @_karm
My endgame is that I don't want to be involved in any of this anymore, ever. I found this entire experience disgusting.
1 reply 0 retweets 6 likes
There are literally entire divisions at Microsoft who are being paid collectively tens of millions of dollars to manage their employees' emotional state. They have managers. They have HR. They have corporate training.
-
-
If literally they cannot themselves teach their developers to reply to a bug report with "thanks, we'll look into this" and not reply until they know what they're talking about, or "sorry, that's not a priority item for us" and close it, then I don't know what to say.
2 replies 0 retweets 5 likes -
Like just take a few minutes of your giant corporate training to say, "hey, when a customer files a bug report, don't try to delegitimize it by 'explaining' why it's not a valid report, or their opinions are wrong. Just accept the bug report, take action, and move on."
1 reply 0 retweets 8 likes - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.