Elon Musk says he fired engineer who corrected him on Twitter
1–10 of 31 posts
Re: Elon Musk says he fired engineer who corrected him on Twitter
#2Re: Elon Musk says he fired engineer who corrected him on Twitter
#3As long as you know it's unacceptable then it makes standing up an act of bravery. If you think it's dunk-on-the-man time because of groupthink and collective disdain then you'll likely be surprised by the consequences.
Re: Elon Musk says he fired engineer who corrected him on Twitter
#4Publicly calling your CEO out like that will generally get you fired. It would be newsworthy if the engineer didn't get released.
Re: Elon Musk says he fired engineer who corrected him on Twitter
#5Publicly calling your CEO out like that will generally get you fired. It would be newsworthy if the engineer didn't get released.
Re: Elon Musk says he fired engineer who corrected him on Twitter
#6The fact these people don't realize this kind of behavior is unacceptable is ironic considering they've been censoring everyone else's for years. As long as you know it's unacceptable then it makes standing up an act of bravery. If you think it's dunk-on-the-man time because of groupthink and collective disdain then you'll likely be surprised by the consequences.
Someone from Reddit also offered him a job* and seemed understanding of what he did.
* https://twitter.com/softwarejameson/status/15920206816882442...
Re: Elon Musk says he fired engineer who corrected him on Twitter
#7https://twitter.com/EricFrohnhoefer/status/15919687831489208...
Re: Elon Musk says he fired engineer who corrected him on Twitter
#8The Android engineer didn't seem to know the difference between an RPC and a request from an end user client. The former timeline engineer disabled public responses to his tweet and has refused to elaborate. Neither of them backed up their contradiction with a rebuttal.
Edit: Was curious so did some digging and found more:
> @elonmusk:
> I was told ~1200 RPCs independently by several engineers at Twitter, which matches # of microservices. The ex-employee is wrong.
> Same app in US takes ~2 secs to refresh (too long), but ~20 secs in India, due to bad batching/verbose comms. Actually useful data transferred is low.
> Part of today will be turning off the “microservices” bloatware. Less than 20% are actually needed for Twitter to work!
> And we will finally stop adding what device a tweet was written on (waste of screen space & compute) below every tweet. Literally no one even knows why we did that …