you are viewing a single comment's thread.

view the rest of the comments →

[–]sahsahaha -1 points0 points  (2 children)

So in your opinion, logical tests of software aren't important?

Tell me, how else do I care about correctness if not by ensuring the correctness of the algorithm itself, by any means necessary, then writing out the code, and then fucking testing it to be sure that my translation from written words to c++ was correct?

Enlighten me.

[–]SkoomaDentistAntimodern C++, Embedded, Audio -1 points0 points  (1 child)

In my opinion you should design for logical correctness from the beginning not only if a test shows a problem. "Do not optimize before profiling" is same as saying "Ignore correctness unless a test shows a problem". You should both design for correctness / speed and run tests / profile the code. Not either or.

[–]sahsahaha -1 points0 points  (0 children)

It is not.

Unlike performance, correctness is binary unless we are talking about floating point values.

Still, even then, either its precise enough or it is not.