Hacker News new | ask | show | jobs
by dspillett 1086 days ago
> But I don't believe on that because Twitter is a billion dollar company and that kind of mistake is dumb.

This sort of mistake is very common especially when a product is going through a period of change, so it seems very believable to me that recent rate limiting features (or older features that have not been used in a long time or maybe ever) on the backend hadn't been adequately tested to make sure there are no unforeseen side-effects on the front-end when they are activated under pressure.
1 comments
DropInIn 1085 days ago
Very common for start ups with inexperienced devs, not for long standing tech companies with the best and most experienced employees...

Isn't Elon supposed to know this shit himself?

I guess we learned alot about the state of the company as well as elons own coding skills with this event, didn't we?

link
dspillett 1084 days ago
Even in “long standing tech companies with the best and most experienced employees” this sort of issue has been known to fall through the cracks. Twitter has experienced significant staffing changes, procedure changes, and code changes, recently and any one of those three things can exacerbate the chances of side-effects of changes not being realised until too late.
link
DropInIn 1084 days ago
When you buy a company and your staff has had near complete turnover and your product significantly changes (at least in consumers eyes), are you actually the same company?

I'd say that shortly after Elon bought it twitter effectively became a start-up rather than an established company.

Arguing otherwise is like saying Xerox Park would have been the exact same institution even if all the staff were swapped with interns and management fundamentally change mission statements etc.....

Kind of absurd when framed that way, huh?

link