4 ms·

Sure, it's clever enough to swap identifiers correctly, but the shape of the code and techniques it uses were familiar to me from elsewhere, at times. It's not

Sure, it's clever enough to swap identifiers correctly, but the shape of the code and techniques it uses were familiar to me from elsewhere, at times. It's not unlike copying code from stack overflow and swapping the identifiers around.

nl 4y ago
> the shape of the code and techniques it uses were familiar to me from elsewhere. Isn't this exactly what you'd expect an AI coder to do?
- dleslie 4y ago
  That's precisely the problem with it. AI, as it is, can be considered a lossy compression technique with multiple document recovery, convolution and interpolation ability.
  - nl 4y ago
    Can't humans be considered a lossy compression technique with multiple document recovery, convolution and interpolation ability? What is the specific difference?
rolisz 4y ago
How did you learn the shape of the code and techniques that you recognized? By looking at other code? Are you violating copyright when you are writing similar code yourself?
- hakre 4y ago
  > By looking at other code? Are you violating copyright when you are writing similar code yourself? In that order likely a violation, but it depends on the concrete case, always.
- dleslie 4y ago
  From decades of looking at interesting code. I take care to attempt to not duplicate code; it's why don't use copilot.
- int_19h 4y ago
  > By looking at other code? Are you violating copyright when you are writing similar code yourself? It's certainly possible. Back when Phoenix reverse-engineered the IBM BIOS using published sources with a restrictive license, they did it by having one team read the sources and write a very detailed specification of everything that happens there, and then another team used that spec to write new code from scratch. They did it that way because if the first team were to write the code themselves, it is quite likely that the result would be legally considered derived work.

nl 4y ago

> the shape of the code and techniques it uses were familiar to me from elsewhere. Isn't this exactly what you'd expect an AI coder to do?

dleslie 4y ago
That's precisely the problem with it. AI, as it is, can be considered a lossy compression technique with multiple document recovery, convolution and interpolation ability.
- nl 4y ago
  Can't humans be considered a lossy compression technique with multiple document recovery, convolution and interpolation ability? What is the specific difference?

rolisz 4y ago

How did you learn the shape of the code and techniques that you recognized? By looking at other code? Are you violating copyright when you are writing similar code yourself?

hakre 4y ago
> By looking at other code? Are you violating copyright when you are writing similar code yourself? In that order likely a violation, but it depends on the concrete case, always.
dleslie 4y ago
From decades of looking at interesting code. I take care to attempt to not duplicate code; it's why don't use copilot.
int_19h 4y ago
> By looking at other code? Are you violating copyright when you are writing similar code yourself? It's certainly possible. Back when Phoenix reverse-engineered the IBM BIOS using published sources with a restrictive license, they did it by having one team read the sources and write a very detailed specification of everything that happens there, and then another team used that spec to write new code from scratch. They did it that way because if the first team were to write the code themselves, it is quite likely that the result would be legally considered derived work.