4 ms·
The “almost correct” aspect will be especially fun when AIs are used to refactor code. I was thinking about how a future legacy codebase might look like after a
by layer8 4y ago
The “almost correct” aspect will be especially fun when AIs are used to refactor code. I was thinking about how a future legacy codebase might look like after a decade of having AI-generated code added to it, and then of course you would want the AI to apply some refactorings from time to time.
One might argue that it won’t be a problem with proper tests. But do coders want to spend most of their time proofreading AI-generated code and taking care of proper test coverage? That doesn’t sound very appealing.
- plasticchris 4y agoWhy can’t the AI write tests too? Then you can have 100% coverage of your (probably) correct code…
- saulpw 4y agoThat's even worse, because now the tests are wrong too! I asked it for a list of test cases for a particular function I wanted to write, and every single one of the cases it presented was incorrect. So it was worse than useless, now I had to check its work and then do the work myself anyway.
- layer8 4y agoIt can, but you have to proofread those too.
- noobermin 4y agoWhy not generate an AI that can take any code and decide whether it has any errors or not?
- dskrvk 4y agoAn AI that tells whether or not a program will halt.
- ParetoOptimal 4y ago> The “almost correct” aspect will be especially fun when AIs are used to refactor code. Hope your function has all invariants covered with one or more property tests!
- layer8 4y agoI’m sure the AI has added all necessary tests like I told it to!