ditto, similar to the way Severence gets a sense of whats off, i cna do that with code, ask me to start from scratch i would not know where to start. Give me google, i will have a bunch of a copy pasta that works in the end, claude does the research, evaluation, best practices and review and testing and re-review and testing, when the Developers department will go to war with you if you put a Slack question through the wrong channel

So really what you do is guess what the code you read is doing. Which is generally fine.

But how can you be sure in a review that the code will actually work? How can you falsify it? A review is more than just reading code.

FORTRAN inline for loops go brrrrrr