8 ms·

Are you serious? do you know how software development is done? do you know what a repository is? Do you know how to look through repository to find code changes

by water8 4y ago

Are you serious? do you know how software development is done? do you know what a repository is? Do you know how to look through repository to find code changes? Any computer scientist can do that there’s nothing special about Twitter I don’t know why you think that. Twitter could be created by an undergraduate CS major.

prng2021 4y ago
It sounds like you have at least an undergraduate CS degree. Go ahead and recreate Twitter and share your GitHub repo for us to review. No need to rush. I'm happy to wait several decades for you to complete the project.
- water8 4y ago
  I mean how hard could really be since nobody really has access to the fire hose and only gets showing a little bit at a time which is really horizontally scalable. I mean let’s do the math when NVME Drive can write at 4gbps so scale that to match the influx of data rate with room to spare. The point is Tesla engineers are going to look for nefarious action, not to worry about corner cases. what a non sequitur argument that is
- water8 4y ago
  And the code is not the hard part it’s the scaling in the architecture to handle the rate at which the data will flow.
rgavuliak 4y ago
There is a reason the best practice is not to do huge PRs because it's very difficult to review. Now imagine one person has to review all the code generated by a company such as Twitter with 3k+ Engineers across multiple years. Is that even possible given the cognitive load? If so how long would it take to produce anything meaningful?
- water8 4y ago
lamontcg 4y ago
> Twitter could be created by an undergraduate CS major. All the codebases will look like they were created by an undergrad CS major and then have accumulated 16 years of edge conditions. And if you pull it all down and try to rewrite it because it is all overly complicated and everyone who built it was wrong: https://fs.blog/chestertons-fence/ https://fs.blog/chestertons-fence/
- water8 4y ago
  Oh, please there’s not that many edge conditions to Twitter for God sakes. It’s not Google.
  - lamontcg 4y ago
    https://xkcd.com/793/ https://xkcd.com/793/

by water8 4y ago

prng2021 4y ago

It sounds like you have at least an undergraduate CS degree. Go ahead and recreate Twitter and share your GitHub repo for us to review. No need to rush. I'm happy to wait several decades for you to complete the project.

water8 4y ago
I mean how hard could really be since nobody really has access to the fire hose and only gets showing a little bit at a time which is really horizontally scalable. I mean let’s do the math when NVME Drive can write at 4gbps so scale that to match the influx of data rate with room to spare. The point is Tesla engineers are going to look for nefarious action, not to worry about corner cases. what a non sequitur argument that is
water8 4y ago
And the code is not the hard part it’s the scaling in the architecture to handle the rate at which the data will flow.

rgavuliak 4y ago

There is a reason the best practice is not to do huge PRs because it's very difficult to review. Now imagine one person has to review all the code generated by a company such as Twitter with 3k+ Engineers across multiple years. Is that even possible given the cognitive load? If so how long would it take to produce anything meaningful?

water8 4y ago

lamontcg 4y ago

> Twitter could be created by an undergraduate CS major. All the codebases will look like they were created by an undergrad CS major and then have accumulated 16 years of edge conditions. And if you pull it all down and try to rewrite it because it is all overly complicated and everyone who built it was wrong: https://fs.blog/chestertons-fence/ https://fs.blog/chestertons-fence/

water8 4y ago
Oh, please there’s not that many edge conditions to Twitter for God sakes. It’s not Google.
- lamontcg 4y ago
  https://xkcd.com/793/ https://xkcd.com/793/