← Back to context

Comment by shakna

2 months ago

Requiring you to audit both security and robustness on the LLM generated code.

Creating two problems, where there was one.

6 comments

shakna

Reply
bennyg  2 months ago

I didn't say generate :) - in all seriousness, I think you could reasonably have it copy the code for e.g. lodash.merge() and paste it into your codebase without the headaches you're describing. IMO, this method would be practical for a majority of npm deps in prod code. There are some I'd want to rely on the lib (and its maintenance over time), but also... a sort function is a sort function.

  • shakna  2 months ago

    LLMs don't copy and paste. They ingest and generate. The output will always be a generated something.

    • lgas  2 months ago

      You can give an LLM access to tools that it can invoke to actually copy and paste.

    • TheBicPen  2 months ago

      In 2022, sure. But not today. Even something as simple as generating and running a `git clone && cp xyz` command will create code not directly generated by the LLM.

      1 reply →