Live data from Hacker News

Twitter Is DDOSing Itself

sfba.social

871–880 of 1001 posts

Re: Twitter Is DDOSing Itself

#871

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!"

Indeed, if a dumb computer can understand the code and execute it flawlessly then so can you! /s

Re: Twitter Is DDOSing Itself

#872
post #769

Earlier quoted context omitted.

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 mode…

Wechat isn't a subscription model. It is money tized exactly the same way as Twitter, advertising.

Re: Twitter Is DDOSing Itself

#873

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…

What do you do when people decide to make the exact ama E mistake again?

If you can’t refer to “last time this was disaster” (aka “I told you so”) how do you prevent it.

Re: Twitter Is DDOSing Itself

#874
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.

In this job market, it's hard. And many engineers are on H1B visas so it's even harder to jump ship.

This is the strongest job market for job seekers in about 60 years.

Re: Twitter Is DDOSing Itself

#877

Earlier quoted context omitted.

google wouldn't just shut off services for a big customer like that...

Don't you have to pay your bill to be considered a customer?

Legally no, you are a customer if you have a contract .

same way we are a tenant( and have rights) even if you don’t pay rent.

Disputes are resolved via arbitration and courts , no payment does not give GCP ( or any vendor) unilateral right to terminate (the contract however possibly might ) .

Usually vendor has to give notice of termination and there would be a time window before termination can occur .

Unpaid dues are like unpaid mortgage there are many steps before the vendor can get a court to force the party to make payment or seize assets in lieu

Re: Twitter Is DDOSing Itself

#879

Earlier quoted context omitted.

> The people at Twitter who understood the system and could predict the side effects were all fired or left. You have zero idea if that is true or not.

The current state of Twitter seems to indicate there's a significant problem with the code, which implies the people who would have either spotted that before it was deployed or fixed it quickly afterwards, are unable to do so. Given the number of layoffs and resignations Occam's Razor would suggest the reason is because those people aren't available to do that work. We don't kmow it's true but it is a likely explana…

But these are "significant problems with the code" which evidently can't be fixed by simply reverting relevant changes. In that case, it seems more likely to me that these are due to long-standing issues which would have caught up to the company sooner or later.

Re: Twitter Is DDOSing Itself

#880

Earlier quoted context omitted.

Well "forced to execute" is somewhat subjective. If you are convinced leadership is doing the "wrong thing," then best to either leave or accept that you're just collecting your paycheck. In the case of Twitter, the new owner has thoroughly broken the advertising business and is trying to aggressively pursue a new version of the data business Twitter once had-- E.g. Google's Caffeine, which Twitter also eventually lo…

I don't understand why anyone, at any job that is not C-level, has an attitude of anything other than collecting your paycheck. I care about my professional reputation and my career, but I don't care at all about the well-being of the company that has hired me to perform some task. I will advise to the best of my ability, but if they blow themselves up, why should I lose any sleep? That's their problem, not mine. Det…

This is healthy but some of us find themselves in a position where caring about the company has tangential benefits like bonuses, stock options, que promotions and other objectives with a well defined incentive for you to personally care about it.
Post reply on HN