News for hackers. Stuff that matters.

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

Re:Tesla engineers were on-site to evaluate the Twitter staf... by krashidov on Sunday October 30, 2022 @03:42AM (#33392115)
Honest question - have you ever worked on a codebase with 0 bugs? I don't think that's feasibly. What you're asking for is an infallible god-like programmer.

You will always have bugs. The best engineers can solve the hardest bugs

[ Parent | on HN ]
Re:Tesla engineers were on-site to evaluate the Twitter staf... by 411111111111111 on Sunday October 30, 2022 @04:45AM (#33392480)
How did you get from "less bugs" to "0 bugs"?
[ Parent | on HN ]
Re:Tesla engineers were on-site to evaluate the Twitter staf... by cudgy on Sunday October 30, 2022 @07:32AM (#33393494)
Maybe because there’s a bug in your statements. You use “no bugs” and “less bugs” to describe the same point.
[ Parent | on HN ]
Re:Tesla engineers were on-site to evaluate the Twitter staf... by 411111111111111 on Monday October 31, 2022 @05:38AM (#33403637)
True, my autocorrect added an extraneous "s" to the first sentence. It's amazing how some people bend over just to create a narrative they can argue against.
[ Parent | on HN ]
Re:Tesla engineers were on-site to evaluate the Twitter staf... by learningstud on Saturday November 05, 2022 @11:45AM (#33482560)
It's feasible to create no bugs with formal specification and formal verification. For example, with Lean 4, one can add a proof for each array-access-by-index that the index is within the bound of the associated array. Every aspect of the codebase can be subject to formal proofs that are verified by the compiler. See also CompCert and Sel4.
[ Parent | on HN ]