3 ms·
I am struggling to teach AI to stop dreaming up APIs which don't exist and failing to solve relatively simple but not often written about problems. It's good w
by Arch-TK 2y ago
I am struggling to teach AI to stop dreaming up APIs which don't exist and failing to solve relatively simple but not often written about problems.
It's good when it works, it's crap when it doesn't, for me it mostly doesn't work. I think AI working is a good indicator of when you're writing code which has been written by lots of other people before.
- Terr_ 2y ago> I think AI working is a good indicator of when you're writing code which has been written by lots of other people before. This is arguably good news for the programming profession, because that has a big overlap with cases that could be improved by a library or framework, the traditional way we've been trying to automate ourselves out of a job for several decades now.
- joshka 2y ago>I am struggling to teach AI to stop dreaming up APIs which don't exist and failing to solve relatively simple but not often written about problems. Try giving them more context of APIs that actually exist then as part of the inputs...
- mkl 2y agoHow do you do that when you don't know the APIs? AI code assistants seem more useful when you're doing something outside your existing experience: different domain, different libraries, different language, etc.
- joshka 2y agoI use GitHub CoPilot both in and ouside my existing experience. Mostly I'm working with Rust, so access to the API surface of a library is fairly simple (docs.rs/cratename) and something which can be provided to the context by pasting if needed. YMMV for other languages.
- Arch-TK 2y agoIt doesn't help even if I paste the code in sometimes.