SV, or at least the successful companies, have a very extensive process for code verification. You praise airliners but you forget how many delays, gare changes, lost luggage’s they deem acceptable.
-
-
Replying to @bertil_hatt @zeynep
Let's make a distinction between local engineering decisions & in-the-market behaviour. We don't have equivalent of code verification for social & ecosystemic effects. These guys have those processes. Musk didn't engage w people who cld help w that. That's what could be learned.
1 reply 0 retweets 0 likes -
The code inside that sub was no doubt watertight. The domain experts are on record as saying the way that the sub related to the ecosystem was absolutely not.
1 reply 0 retweets 1 like -
Replying to @__stillPoint @zeynep
Musk did communicate with someone who he thought was on the ground. All SV companies hire UX researchers to do the same. Data analytics has less empathy, but does the same. Claiming otherwise is just denying the existence of not one but two entire lines of work.
3 replies 0 retweets 0 likes -
You and Zeynep, and a majority of journalists are confusing two things: - these companies should (and do) listen to their users, very intently; - they should listen and respond to you. You all sound very hurt they don’t. I’m saying: some try but we end up victims of your tone.
1 reply 0 retweets 0 likes -
Replying to @bertil_hatt @zeynep
I don't think that characterises the problem here. This isn't about "listening to users". I don't know how anyone could turn this case into a parable about listening to users.
1 reply 0 retweets 0 likes -
Replying to @__stillPoint @zeynep
> We don't have equivalent of code verification for social & ecosystemic effects. I responded to this point. The ecosystem for social media is the users.
1 reply 0 retweets 0 likes -
Replying to @bertil_hatt @zeynep
I don't think Elon Musk has a lot to do with social media. But, e.g. Facebook has repeatedly been (recklessly) experimental in the way it deals with social issues and issues of consent - its ecosystem.
2 replies 0 retweets 0 likes -
That doesn't look like cautious engineering. That looks like pushing experimental code into the dev branch.
2 replies 0 retweets 0 likes -
Replying to @__stillPoint @zeynep
That’s not why I saw. I participated in many experiments where Facebook had clear, isolated protocols outside of “dev branch” or whatever that is. They didn’t communicate about it explicitly because of misinformed moral outrage, naming people who are still missing the point.
1 reply 0 retweets 0 likes
They can’t just test software—they are in the people business, just bia tech. I’m not saying their code is buggy, I’m saying their feature release and expansion speed is recklessly fast. Also buggy code because “must ship quickly” is real in the industry—not the giants anymore.
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.