this post was submitted on 25 Jul 2023
382 points (97.8% liked)
Enough Musk Spam
2956 readers
5 users here now
For those that have had enough of the Elon Musk worship online.
No flaming, baiting, etc. This community is intended for those opposed to the influx of Elon Musk-related advertising online. Coming here to defend Musk or his companies will not get you banned, but it likely will result in downvotes. Please use the reporting feature if you see a rule violation.
Opinions from all sides of the political spectrum are welcome here. However, we kindly ask that off-topic political discussion be kept to a minimum, so as to focus on the goal of this sub. This community is minimally moderated, so discussion and the power of upvotes/downvotes are allowed, provided lemmy.world rules are not broken.
Post links to instances of obvious Elon Musk fanboy brigading in default subreddits, lemmy/kbin communities/instances, astroturfing from Tesla/SpaceX/etc., or any articles critical of Musk, his ideas, unrealistic promises and timelines, or the working conditions at his companies.
Tesla-specific discussion can be posted here as well as our sister community /c/RealTesla.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How did this even pass to production, do they just merge shit to main and pray to God it works?
Whenever you see this sort of technical problems from Twitter. Remember that Musk fired almost all of his staff. Including software engineers.
And the ones he didn’t fire left en mass. At least the ones not tied down by visas and/or other red tape
You underestimate the laziness of the typical office worker.
I am one of those lazy ass office workers lol. I’m sitting here at work on Lemmy, but even I would have been jumping off that sinking ship a long while ago.
When I think about it, this is actually exactly the kind of bug that very easily passes to production.
You have your dev environment; something like "katanasdevmachine.twitterdev.com", where you do your work and verify bugs. This environment is configured with a developer database, and developer URL configurations. So there might be "katanasdevmachine.twitterdev.com" simulating x.com, and then "briansdevmachine.twitterdev.com" to represent twitter.com. You and Brian do a test of the redirect from there, and all's well.
It's only when you're moving to the genuine domains that small URL-parsing/concatenating bugs might show up. But there's not many easy ways to "simulate" being on the actual twitter.com website with test code you've written. It's doable, just not convenient. So, these sort of URL configs can very often be the one place that bugs essentially go "untested" in an imperfect workflow.
I mean, /etc/hosts, but I see your point. I’d guess this might be a case of, “this is pretty simple, we’re good to go”. then “oops”
Yeah that's true