4 ms·

And for those who say that it doesn't speed up development, then maybe they're right, because the main benefit isn't at speed. It reduce the devs mental / cogni

And for those who say that it doesn't speed up development, then maybe they're right, because the main benefit isn't at speed. It reduce the devs mental / cognitive load and pass it to the ai instead, we just need to check and review the result. If it doesn't monumentally increase the speed, it helps devs to stay productive longer

frizlab 2y ago
Reviewing code is famously harder than writing it. I don’t see how it’s a gain to have to review more code than to write.
- KaoruAoiShiho 2y ago
  It's shorter, you're working directly with the code base you're already thinking about, and it's plugged into it rather than having to start a new mental task when you're looking at a pull request.
  - 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 ago
      When 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 ago
      For 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.
- fendy3002 2y ago
  In some cases where I often use it I find it easy. Usually I give an ORM class and ask it to parse to mysql / postgres create table. Tedious tasks and easy to review. Another time I asked to generate a code to listen to SMTP server using a library, and again it's easier to review because I was not familiar with the library. From that I can make my own adjustment.

frizlab 2y ago

Reviewing code is famously harder than writing it. I don’t see how it’s a gain to have to review more code than to write.

KaoruAoiShiho 2y ago
It's shorter, you're working directly with the code base you're already thinking about, and it's plugged into it rather than having to start a new mental task when you're looking at a pull request.
- 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 ago
    When 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 ago
    For 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.
fendy3002 2y ago
In some cases where I often use it I find it easy. Usually I give an ORM class and ask it to parse to mysql / postgres create table. Tedious tasks and easy to review. Another time I asked to generate a code to listen to SMTP server using a library, and again it's easier to review because I was not familiar with the library. From that I can make my own adjustment.