Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

Re:Tesla engineers were on-site to evaluate the Twitter staf... by rl1987 on Sunday October 30, 2022 @08:45AM (#33393993)

This is pretty much like saying that Dropbox can be trivially replicated with rsync(1) or that one can code Uber in a weekend. Perhaps you can do so at small scale for yourself and your friends. The essence of Twitter (or Dropbox, or Uber) is indeed quite simple.

However there's orders of magnitude more effort that goes into:

* Usability

* Performance

* Stability

* Security

* Localisation/internationalisation and accounting for cultural differences

* Monetisation - ads, payment platform integration, fighting fraud

* Fighting abuse, both automated and not

* ... and thousands of little things that will come up when building something big.

Think of this another way... Twitter would not employ literally thousands of employees if there was nothing for them to do. It is not a charity. I don't buy that building anything that can handle hundred of millions of users is simple.

[ Parent | on HN ]

Re:Tesla engineers were on-site to evaluate the Twitter staf... by mousetree on Sunday October 30, 2022 @09:48AM (#33394480)

These are all valid points but none speak to GP's comment that the scale aspect is no longer as difficult to solve.

[ Parent | on HN ]

Re:Tesla engineers were on-site to evaluate the Twitter staf... by rl1987 on Sunday October 30, 2022 @10:33PM (#33401430)

One can say that aforementioned classes of problems are semantically, conceptually different from scalability, but they will inevitably come up when building something the scale of Twitter and will require mountains of technical work to deal with.

[ Parent | on HN ]