881–890 of 1001 posts
Here's a guy who understands what's REALLY going on: https://twitter.com/i/status/1675254646942896128
"Something went wrong. Try reloading" Man, we do need a public square.
At least if it's blocking me from viewing the tweet's comments, returns me some decent messages. But no, just a plain "Something went wrong." like a hackathon page.
Earlier quoted context omitted.
> The people at Twitter who understood the system and could predict the side effects were all fired or left And never created sufficient testing.
There is never sufficient testing. If there is, then you have a formal proof for your algorithm.
It's not just hypothetical either. There was a bug in a sorting algorithm a few years back that had been 'proved' correct. I think it was to do with numbers wrapping, and that hadn't been considered in the mathematical proof.
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.
This rhetoric is well past its peak. When the firings happened, people said twitter would crash in a week. It's been a long time since then, and twitter, for my very generic uses and purposes, has just gotten better. Demonizing past hard decisions at every unrelated point of difficulty has to be the worst kind of toxicity there is.
Interesting. My "generic uses and purposes" was to occasionally scroll around through tweets somebody linked me to.
That's entirely impossible now since I don't have an account (and don't plan to create one).
Roughly speak, it has become infinitely worse for me.
Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement. Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof. I can of…
[flagged]
In fact, I'd recommend you do some job hunting right now and get an offer to prove your point.
It is always amazing that some people can be so out of touch and speak to people in this tone.
What I find more ironic than this bug is is that all of these Mastodon evangelists still have Twitter accounts after their Elon meltdown. So much so that they even use it after Twitter stopped public access.
Have you considered that a lot of people use both platforms and don’t really care about the politics of it? Those who do care are very loud (on both platforms) but they might be a minority in practice.
#TwitterDown #MastodonMigration #DDOS #TwitterFail #SelfDDOS
This is why context matters.
Earlier quoted context omitted.
That will be the case once H1-Bs are reformed and universal healthcare becomes real. Until then, this is an unrealistic and cruel position.
Fair point. I was only considering the perspective of US citizens. It does make me wonder how much the ratio of forced labor H1B situations has gone up at Twitter as US citizens all bail from the fire. I cannot imagine why anyone would work there if they had a choice at this point.
Earlier quoted context omitted.
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.
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.
And? These are the hardcore programmers of Twitter 2.0, aren't they?
Earlier quoted context omitted.
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?
Earlier quoted context omitted.
What do you mean?
Jitter is a little randomness in how long clients wait between retries. It ensures that you don't have a "thundering herd" all retrying at the same time. Imagine if your API used exponential backoff of [1s, 2s, 4s, 8s, ...] and a large group of requests gets a retryable error at t=0. They will all retry at exactly t=1, t=2, etc. If the group is large enough that repeated surge of requests can knock you offline. There…