Why Twitter didn’t go down: From a real Twitter SRE

Re:Why Twitter didn’t go down: From a real Twitter SRE by RivieraKid on Tuesday November 22, 2022 @12:51PM (#33708620)

Well that's what I did, I made both iOS and Android version of an app and some of the design.

I mean, a mediocre complexity app doesn't need more than one developer for a "slow improvement mode".

[ Parent | on HN ]

Re:Why Twitter didn’t go down: From a real Twitter SRE by benj111 on Tuesday November 22, 2022 @01:40PM (#33709321)

But Twitter needs more than 5 employees.

How many bug reports do you think the Twitter site and apps get each day? How many employees do you think it takes just to triage them?

[ Parent | on HN ]

Re:Why Twitter didn’t go down: From a real Twitter SRE by RivieraKid on Tuesday November 22, 2022 @02:17PM (#33709936)

You don't have to read all of the bug reports, just a representative sample to discover issues worth fixing.

[ Parent | on HN ]

Re:Why Twitter didn’t go down: From a real Twitter SRE by benj111 on Tuesday November 22, 2022 @03:52PM (#33711344)

How do you get a 'representative' sample?

You still have to read them to work out that user X saying they can't log in is the same as user Y saying authentication is failing at A stage, issue is present on B and C platforms version D.E

Further the issue of 'site using the wrong font' is not equally as important as 'site is exposing private user data'. And you're likely to get many people reporting the former, and maybe only one reporting the latter, so a sample isn't likely to catch the really important stuff.

[ Parent | on HN ]