How programmers make sure that their software is correct

Re:How programmers make sure that their software is correct by commandlinefan on Thursday January 06, 2022 @10:11AM (#29824451)

You can try, though - and demonstrate that you did. I've seen bugs that would have been trivially caught if the software had been run even one time - so it was clear that the software had never been run even one time.

[ Parent | on HN ]

Re:How programmers make sure that their software is correct by gitgrump on Thursday January 06, 2022 @10:48AM (#29825023)

I've had "senior engineers" and engineering directors submit PRs that just flat out don't work. Like, I ran a minimum working example and it just... didn't work. I swear to God, some people are actually professionally negligent at this point.

[ Parent | on HN ]

Re:How programmers make sure that their software is correct by ohwellhere on Thursday January 06, 2022 @10:39AM (#29824899)

This is my favorite. Doesn't even compile, or crashes immediately, and yet... it's somehow in a PR.

[ Parent | on HN ]

Re:How programmers make sure that their software is correct by klyrs on Thursday January 06, 2022 @05:26PM (#29831310)

I've done that. Spend days testing a patch, getting everything just right. Then, as you're doing final touchup, you introduce a syntax error with a wrong keystroke and fail to notice before pushing to the PR branch.

But, of course, this is why we use CI.

[ Parent | on HN ]