4 ms·
When I write code, I usually get a complete understanding of the problem and constraints. I have a picture in my mind of all the edge cases and branching that c
by Seb-C 2y ago
When I write code, I usually get a complete understanding of the problem and constraints. I have a picture in my mind of all the edge cases and branching that can happen, which most of the time allows me to write correct code without bugs.
When I review code, I am completely unable to get this mental picture, and I usually miss a lot of issues that I would otherwise have avoided.
Which is why I don't see the point of Copilot.
- KaoruAoiShiho 2y agoWhen you review pull requests you're unable to get the mental picture. But it's different with copilot because it fits in your mental picture, you can compartmentalize what you're working on, and the copilot output can come in the form of small pieces that are easily understood and slot in the prepared places where you need it. I agree 100% that reviewing human code is a lot of work but not with copilot IMO because of the immediacy of it all.
- aeonik 2y agoFor me to understand what you mean here, I'm going to need examples... for the stuff I work on, the things you are saying here are verifiably impossible. There is no possible way to 1. get a complete picture 2. understand all the constraints because we pull data from the real world, and the real world is constantly changing, and we still don't even have a single theory of everything in physics.