The author did not define what he meant by reasoning about code other than calling it a synonym for "thinking about code". Is it a scam to think about code, fe

The author did not define what he meant by reasoning about code other than calling it a synonym for "thinking about code". Is it a scam to think about code, fellas? I'll provide some examples: * Does code this terminate? * Does this method produce expected output for all possible inputs? * Does this code produce the same output when given the same input? * Does this method leave the system in a bad state if it is cancelled partway through? * Can this method be inlined? * Can this method throw an exception? * Does this method use all of its parameters? * Why did this method not do what I expected it to do? * My tests passed, does that mean my code does what I want it to do? Is it a "scam" to ask any of the above questions? > effort that could better be focussed on checking whether your understanding of the problem is indeed correct, or needs updating. Checking? I checked the code. It looks like code. Did you want me to think about it too? > This points to a need for code to be deletable way faster than it needs to be thought about. I can delete code pretty quickly. I have tools that help me to scam about whether it's safe to delete or not. > choice of programming language is arbitrary Oof. Brainfuck it is, then.