As a former individual who understands the underlying systems, it seems like they botched deployment of a new feature causing issues and cannot figure out how to solve them.
Most of Twitter is and has been in maintenance mode since acquisition (think of 10 man engineering team and 1 left to handle maintenance).
This is why it cracks me up every time when someone is praising Elon for “cutting slack” when firing all those twitter employees. Yes, twitter did not implode immediately. Turns out, people can build software that is stable enough to run in maintenance mode. But good luck dealing with new issues cropping up.
People too far removed from IT/Dev team can become disillusioned as to what they do.
If you have a good dev team, you won’t hear about them doing anything until shit hits the fan. If you haven’t heard from them?… They’re doing their job. Leave them alone.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
It’s not a result of Google storage. Google served only for data analysis and batch jobs. These would not be sufficient enough to cause service degradation. Just a bad launch of a feature (via server side) that had unintended consequences.
As a former individual who understands the underlying systems, it seems like they botched deployment of a new feature causing issues and cannot figure out how to solve them.
Most of Twitter is and has been in maintenance mode since acquisition (think of 10 man engineering team and 1 left to handle maintenance).
This is why it cracks me up every time when someone is praising Elon for “cutting slack” when firing all those twitter employees. Yes, twitter did not implode immediately. Turns out, people can build software that is stable enough to run in maintenance mode. But good luck dealing with new issues cropping up.
People too far removed from IT/Dev team can become disillusioned as to what they do.
If you have a good dev team, you won’t hear about them doing anything until shit hits the fan. If you haven’t heard from them?… They’re doing their job. Leave them alone.
deleted by creator
I don’t think I’ve ever met a former individual. What happened? Was it like a Frankenstein thing?
Former individual is just the politically correct way to say dead guy.
Actually, he pissed of Captain Janeway and was erased from the timeline.
Used to be a nice guy before he became a former individual.
Or he got assimilated by the Borg. No longer an individual lol
Finally the people witty people came from Reddit
presumably they joined a hive mind
Nah, cloning gone wrong.
They federated with others.
From what I read they refused to pay Google for hosting services when the contract was up for renewal…which was June 30th.
A day that will live in Internet infamy.
Last day of the fiscal quarter. Changes tend to happen.
deleted by creator
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I’ve heard.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I’ve heard.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I’ve heard.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I’ve heard.
I’ve heard this multiple times from the same person even
wow me too, what are the odds
That’s just what I’ve heard!
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I’ve heard.
I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.
This is just what I’ve heard.
It’s not a result of Google storage. Google served only for data analysis and batch jobs. These would not be sufficient enough to cause service degradation. Just a bad launch of a feature (via server side) that had unintended consequences.