3 ms·
At Twitter's scale the issues are far less about "this code smells funny" but how dozens of systems interact together. Ain't nobody gonna figure out problems by
by inerte 4y ago
At Twitter's scale the issues are far less about "this code smells funny" but how dozens of systems interact together. Ain't nobody gonna figure out problems by simply checking out a handful of repositories, and specially in a few hours / days.
- Nicksil 4y ago>At Twitter's scale the issues are far less about "this code smells funny" but how dozens of systems interact together. Ain't nobody gonna figure out problems by simply checking out a repository, and specially in a few hours / days. I don't know why you think someone would have to know about Twitter's specific implementation of distributed systems in order to inspect those systems for non-twitter-specfifc issues.
- inerte 4y agoAck, and thanks for your comment. I am choosing to disengage from this conversation, have fun!
- Nicksil 4y ago>Ack, and thanks for your comment. I am choosing to disengage from this conversation, have fun! Sorry, what was it about my comment you vehemently disagree with?
- saagarjha 4y agoIssues such as what?
- Nicksil 4y ago>Issues such as what? Such as those which do not meet the standards defined for the particular audit.
- saagarjha 4y agoI mean, you can do a very general audit of things like “is there CI” or “do they use horribly unsafe serialization everywhere” but I don’t see anything beyond this without a huge amount of effort.
- Nicksil 4y ago>I mean, you can do a very general audit of things like “is there CI” or “do they use horribly unsafe serialization everywhere” but I don’t see anything beyond this without a huge amount of effort. Do we know what is or isn't being reviewed? Do we know how much effort is being applied in this process or if there's a defined upper and/or lower bound?
- saagarjha 4y agoThe upper limit is the point where it makes sense to bring in experts rather than random Tesla engineers.