Earlier quoted context omitted.
That's a non-sequitir. You can be at the top of your field and not completely understand a complex system. Also, the right people may not have even been involved in the implementation of this "feature".
geohot was naively optimistic when he offered his so called "internship" to Musk. Ended up resigning in one month without delivering anything.
Twitter Is DDOSing Itself
671–680 of 1001 posts
Re: Twitter Is DDOSing Itself
#672Earlier quoted context omitted.
They lack knowledge not skills. To my knowledge there is no "intuitively understand how my changes will impact a complex system without studying it" skill (unless that system is under a robust test suite, which Twitter is not)
> knowledge there is no "intuitively understand how my changes will impact a complex system without studying it" skill (unless that system is under a robust test suite, which Twitter is not then how do they have confidence that anything works before they subject hundreds of millions of people around the world to system updates? that seems disrespectful to the user, if you asked me.
Re: Twitter Is DDOSing Itself
#673People commenting that people who are still at Twitter because of their own volition, just stop. Certainly some are still there because they want to be, but there are absolutely people trapped there economically one way or another, working for a tyrant.
I don't think you understand what a "tyrant" is. Companies aren't democracies.
Re: Twitter Is DDOSing Itself
#674Can 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.
What holiday is it?
Re: Twitter Is DDOSing Itself
#675Earlier quoted context omitted.
A union vote is the only way to save that platform. Either unionize or let the company die.
Unions are for the people, not the company
Re: Twitter Is DDOSing Itself
#676Earlier 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. You have zero idea if that is true or not.
Now me... I know someone personally who was a senior exec for Twitter's software team, who left after Elon's purge.
He left because all the people who understood the system and could predict the side effects were fired or left. He'd been with companies going through death spirals before, and had no interest in being involved with another one.
So, while the person you're replying to might not know, my friend DOES know.
Re: Twitter Is DDOSing Itself
#677Earlier quoted context omitted.
From previous stories about Elon, telling him he’s wrong is a guarantee you’re going under that bus.
Every person in power is told he's wrong every day, all day, by most everyone. Heck, I've hired people to teach me things, told them they were wrong, and learned the hard way, many times.
Re: Twitter Is DDOSing Itself
#678Earlier quoted context omitted.
> 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?
That's a non-sequitir. You can be at the top of your field and not completely understand a complex system. Also, the right people may not have even been involved in the implementation of this "feature".
It's very easy to get caught in assumptions like, "Nobody would ever do things THIS way, so they must have built it THAT way," only to find out that, once upon a time, THIS way was the right way to do things, only for it to over time become less and less optimal, but the costs of changing things were too high to fix it. Once your system is old enough and large enough, you'll have several thousand things just like that.
Re: Twitter Is DDOSing Itself
#679Earlier quoted context omitted.
Putting the personality of the owner aside, they have been running an experiment for the last few months on how to operate a tech company, overworking your engineers and treating them like replaceable automata. Do you want them to succeed and set that as an example for others to follow?
Every social network and large tech company has awful people running it? And I'm yet to see anything beyond "an anonymous source" on this apparent overworking. If you work for a large US tech company, you are replacable automata. How do people not know this? Am I the crazy one here?
Re: Twitter Is DDOSing Itself
#680Speaking 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…
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…
lol nobody would do this to solve this problem because it doesn't even remotely solve it or give the appearance of solving it, if anything it's guaranteed to make things go slower