Live data from Hacker News

Twitter Is DDOSing Itself

sfba.social

761–770 of 1001 posts

Re: Twitter Is DDOSing Itself

#761

> There must have been an insane nest of logic that the devs had to tiptoe through to make the service workable as a private only service. It seems that this statement can lead to different conclusions based on one's biases for or against Musk / freedom of speech: 1) The code base is a mess because the smaller, current team don't know what they're doing and/or management (i.e. Musk) is pushing them too hard and makin…

This makes me realize "the code base is a mess" has been so overused it could be a standard greeting in our profession.

Everyone has their horror story and extreme examples, but for any mildly profitable company that went through a decade or more of operation, I think it's kinda of a meaningless statement.

Re: Twitter Is DDOSing Itself

#762
post #572
post #413

Can we please recognize that this is a holiday weekend and Elon rammed a big release forcing his engineers to come in and iterate multiple patches over the last 12 hours.

Twitter Engineers have had over a year to get out and find another job. At this point the terms of their employment and the expectations from their boss are all crystal clear. Hard to sympathize with those who continue to stick around for whatever reason.

You are telling people who are being abused that it's their fault that they didn't leave. This is victim blaming.

Re: Twitter Is DDOSing Itself

#763
I'm astounded it took this long to finally die. All those Twitter engineers who were harassed by Elmo's very online fan club, and were treated with such cruelty and disdain on their way out, clearly did an incredible job. Hats off to them.

The curse of IT Operations: if you do everything right, management grifters never think you did anything at all. Why do I need you? Everything works fine!

Most Internet platforms are put together by popsicle sticks and bubble gum. If Reddit didn't have 2000 full time employees babysitting that steaming POS, it would be offline by the end of the week. But Twitter was like a chicken running around with its head chopped off, and it didn't stop running for 9 months. It's a testament to how incredible those engineers were.

This collapse at Twitter should have happened by January. It's a real shame it didn't. How many thousands of tech workers were laid off because Musk's fellow parasitic oligarchs saw Twitter running "fine" after the lobotomy, and followed him off the cliff like a bunch of lemmings? How many billions of dollars has the economy lost because of this one despicable man?

Elon Musk is a fraud. He is not an engineer. He's a lazy bum who mooched his whole life off his groomer daddy's apartheid emerald money. He would be nothing without that disgusting, incestuous old man. Despite his enormous financial privilege, Elmo was too lazy to enter the US legally. He was in the US for many years as an illegal immigrant. He only bothered to get off his lazy ass and finish his Economics degree because the risk of his deportation was becoming a real problem for X.com. That crooked philistine doesn't know the first thing about hard work, engineering, or finance. He's a damn good conman, he's good at shitposting, and that's about it. He has no other skills. He is not an engineer. He has no STEM degree. His only real accomplishment in life is proving that you can, in fact, spend billions of dollars in one lifetime, if you simply buy a bird app, run it into the ground, and salt the earth behind it.

Re: Twitter Is DDOSing Itself

#764

Earlier quoted context omitted.

The people at Twitter who understood the system and could predict the side effects were all fired or left. My guess is Elon said "the site's too slow!" Engineers noticed that the home feed request was slow. They didn't understand how it worked, had no tools to profile it, and were given an unrealistic deadline to fix it. So about the only thing they could do was issue multiple, parallel requests and hope that at leas…

>The people at Twitter who understood the system and could predict the side effects were all fired or left Not necessarily. I’ve predicted bad outcomes for decisions in a few cases and been ignored but stuck around regardless. Mostly because I like my job and the goals of my organization even if it makes bad decisions. Of course to remain productive and improve my influence in future decision making it is absolutely…

> Mostly because I like my job and the goals of my organization even if it makes bad decisions.

Keep in mind that Musk intentionally turned Twitter completely upside down. Anything that people there liked about it before Musk is likely gone—coworkers, WFH, perks.

Re: Twitter Is DDOSing Itself

#765

Earlier quoted context omitted.

The people at Twitter who understood the system and could predict the side effects were all fired or left. My guess is Elon said "the site's too slow!" Engineers noticed that the home feed request was slow. They didn't understand how it worked, had no tools to profile it, and were given an unrealistic deadline to fix it. So about the only thing they could do was issue multiple, parallel requests and hope that at leas…

>The people at Twitter who understood the system and could predict the side effects were all fired or left Not necessarily. I’ve predicted bad outcomes for decisions in a few cases and been ignored but stuck around regardless. Mostly because I like my job and the goals of my organization even if it makes bad decisions. Of course to remain productive and improve my influence in future decision making it is absolutely…

People didn’t leave because of the bad decisions. They left because Musk said he wanted “hardcore” people who’d work 80 hour weeks. Turns out masochism isn’t correlated with great engineering.

Re: Twitter Is DDOSing Itself

#766

> There must have been an insane nest of logic that the devs had to tiptoe through to make the service workable as a private only service. It seems that this statement can lead to different conclusions based on one's biases for or against Musk / freedom of speech: 1) The code base is a mess because the smaller, current team don't know what they're doing and/or management (i.e. Musk) is pushing them too hard and makin…

This makes me realize "the code base is a mess" has been so overused it could be a standard greeting in our profession. Everyone has their horror story and extreme examples, but for any mildly profitable company that went through a decade or more of operation, I think it's kinda of a meaningless statement.

> This makes me realize "the code base is a mess" has been so overused it could be a standard greeting in our profession.

I'm printing up t-shirts already, pre-order now and get 10% off the insane nest of logic tee while stocks still last!

Re: Twitter Is DDOSing Itself

#767
post #762
post #572

Earlier quoted context omitted.

Twitter Engineers have had over a year to get out and find another job. At this point the terms of their employment and the expectations from their boss are all crystal clear. Hard to sympathize with those who continue to stick around for whatever reason.

You are telling people who are being abused that it's their fault that they didn't leave. This is victim blaming.

Are you really considering a tough work environment at a high tech company to be abuse? At company that little voluntarily choose to be employed at?

Do you know what conditions are like in most jobs?

Re: Twitter Is DDOSing Itself

#768

Earlier quoted context omitted.

The people at Twitter who understood the system and could predict the side effects were all fired or left. My guess is Elon said "the site's too slow!" Engineers noticed that the home feed request was slow. They didn't understand how it worked, had no tools to profile it, and were given an unrealistic deadline to fix it. So about the only thing they could do was issue multiple, parallel requests and hope that at leas…

> The people at Twitter who understood the system and could predict the side effects were all fired or left. Are you saying the engineers who are now at Twitter don’t have the right skills?

The quote doesn’t say that at all

Re: Twitter Is DDOSing Itself

#769
post #692

Earlier quoted context omitted.

> My guess is Elon said "the site's too slow!" Seems more like a thinly disguised attempt to force people to purchase subscriptions. Blue checkmarks and all.

That's the first thing that came to mind. It's a pay-to-play move, which is not at all surprising. People seem to forget that fully-featured social media-centric corporations are run for profit, and if they can't get enough advertising to balance the books, then what's left but subscriptions? Sometimes people buy media corporations because they're interesting in using them to promote their other more lucrative operat…

> then what's left but subscriptions?

The WeChat model is the obvious answer to that rhetorical question. Build paid services on top of your hellsite with millions of addicts using it daily. For example, Twitter could have easily been the gateway to OnlyFans, or to Patreon. Apple is another example of this kind of value-added ecosystem that leverages a foothold to sell other crap to people.

Or there's the TikTok model: gobble up all the data, sell data to governments, give MBS or Putin admin access to Twitter, build AI on top of the dataset.

Even a private equity chop-shop like Bain could do a better job of extracting value from Twitter than this mess.

This isn't a profit-seeking venture for Musk. This is about politics, about power, and primarily about revenge. Musk is giving Notch stiff competition for the title of most pathetic billionaire.

Re: Twitter Is DDOSing Itself

#770

Earlier quoted context omitted.

About 80% of Twitter was laid off or quit. I think it's a reasonable supposition that a good number of those were critical personnel who felt they could get a better deal somewhere else.

"But the code is self-documenting!"

Of course. The machines get it. And do exactly as commanded. ;)
Post reply on HN