Kevlin HenneyApr 3, 2023

Code generated from LLMs is going to need more testing than code written by developers. This seems self-evident to me, but I suspect a lot of people are going to learn it (or ignore it) the hard way.

Given that most existing codebases are not well tested, and most developers don't test, this does not bode well.

Show threadKevlin HenneyApr 3, 2023
The practical consequence of using LLMs to generate code is that many developers will find they have unwittingly moved themselves into a role they were probably trying to avoid: they have automated the creation of legacy code and have redefined their job role as debugging and fixing such code.
Show threadMatthew MartinApr 11, 2023
@kevlin All code is legacy code that needs to be debugged. There was never a time when people could just write code and choose to not make mistakes.
Show threadsamApr 16, 2023
@mistersql @kevlin It is true that llm generated code is going to need more, and probably different, review than code written by the actual people on your team
Show threadsamApr 16, 2023
@mistersql @kevlin It’s never been a better time for folks to get into property based testing, probably
Show threadsamApr 16, 2023
@mistersql @kevlin an LLM prompt that produces a piece of code that solves a real world problem according to a defined set of specifications is just a program written in a very high level language and the people who are trained in understanding real world problems in a way that translates to prompts like that are programmers
Show threadsamApr 16, 2023
@mistersql @kevlin It’s not even a different skillset just a new programming paradigm
Show threadsam
@mistersql @kevlin I’m super skeptical of these tools but generating certain types of code under certain conditions is probably going to be one of the use cases that ends up being worthwhile
Apr 16, 2023 at 2:08pmWeb