News for hackers. Stuff that matters.
Re:Tesla engineers were on-site to evaluate the Twitter staf... by Aeolun on Saturday October 29, 2022 @08:12PM (#33389343)
If I see the SpaceX code, and it’s full of thousand line functions with a cognitive complexity of 200 I can confidently say it’s going to be hard to maintain.

Clearly it gets rockets into the sky, but something similar is true for all code that hasn’t failed catastrophically yet.

Re:Tesla engineers were on-site to evaluate the Twitter staf... by arrow7000 on Saturday October 29, 2022 @08:26PM (#33389451)
Is there any reason to suspect that Twitter's code will be of this terrible quality? If not, then again: what's the point of bringing random engineers in to take a look at code from an entirely unfamiliar domain?
Re:Tesla engineers were on-site to evaluate the Twitter staf... by Aeolun on Sunday October 30, 2022 @12:25AM (#33391063)
Since it’s a huge enterprise with hundreds of engineers, I don’t have to guess. It’s just a matter of magnitude.
Re:Tesla engineers were on-site to evaluate the Twitter staf... by XorNot on Saturday October 29, 2022 @09:10PM (#33389818)
Except you would be wrong. Or at least not obviously right: safety critical code does all sorts of weird things in the interests of verifiability because it must be exactly right: it doesn't get "maintained", because once it's flight proven you do not change it without an entirely new verification process.

This also leads to interesting practices at times like favouring repeating code over writing separate functions to ensure the flow of reading doesn't jump around and instead always moves forward.