> Isn't analysing and writing bits of code one of the few things LLMs are actually good at and useful for
Absolutely not.
I just wasted 4 hours trying to debug an issue because a developer decided they would shortcut things and use an LLM to add just one more feature to an existing project. The LLM had changed the code in a non-obvious way to refer to things by ID, but the data source doesn't have IDs in it which broke everything.
I had to instrument everything to find where the problem actually was.
As soon as I saw it was referring to things that don't exist I realised it was created by an LLM instead of a developer.
LLMs can only create convincing looking code. They don't actually understand what they are writing, they are just mimicking what they've seen before.
If they did have the capacity to understand, I wouldn't have lost those 4 hours debugging its approximation of code.
Now I'm trying to figure out if I should hash each chunk of data into an ID and bolt it onto the data chunk, or if I should just rip out the feature and make it myself.
Absolutely not.
I just wasted 4 hours trying to debug an issue because a developer decided they would shortcut things and use an LLM to add just one more feature to an existing project. The LLM had changed the code in a non-obvious way to refer to things by ID, but the data source doesn't have IDs in it which broke everything.
I had to instrument everything to find where the problem actually was.
As soon as I saw it was referring to things that don't exist I realised it was created by an LLM instead of a developer.
LLMs can only create convincing looking code. They don't actually understand what they are writing, they are just mimicking what they've seen before.
If they did have the capacity to understand, I wouldn't have lost those 4 hours debugging its approximation of code.
Now I'm trying to figure out if I should hash each chunk of data into an ID and bolt it onto the data chunk, or if I should just rip out the feature and make it myself.