> You can have bugs in the english (or whatever your native language is) description of what you think the algorithm should be doing. According to the principl

> You can have bugs in the english (or whatever your native language is) description of what you think the algorithm should be doing. According to the principle of separation of concerns, this isn't the programmer's problem. > You can prove a program does what the types say it should do but that is not what "correctness" means. Of course, the ultimate arbiter of what “correctness” means is the program specification.