Then most developers you know are subpar. Frontier models routinely write far worse code than I. And I am only a moderately decent dev.
I have even seen llm code generated with a frontier model that blew straight through array boundaries without a worry in the world.
They can be useful at work, especially for tech I know little about, and as an additional set of eyes to avoid easy mistakes like off by ones, or doing wrong pointer arithmetic, but they are pretty abysmal at code generation.
True, but what I mean is that it can find ways to do what I need to do even for things that I don’t know a lot about. If the “solution” it finds ends up being a bunch of hacks I change my approach. If it finds supported and documented APIs, I read their documentation and make sure that my mental model of the the things I’ve just learned about matches the code and explanation from the llm, and if they do I rewrite the code in a way that makes sense and iterate from there.
I also don’t copy paste the code and rewrite it inline. I rewrite it in a different window from scratch. The llm is confined to its browser window.
Essentially, I use these things the way I used to use google a few years ago: searching for documentation and examples. That is no longer possible with today’s search engines.
I thought the same earlier this year. Opus 4.8 mostly produced garbage code in my eyes. Then Opus 5.5 came and now it can routinely produce about the same quality as me but much faster.
Then most developers you know are subpar. Frontier models routinely write far worse code than I. And I am only a moderately decent dev.
I have even seen llm code generated with a frontier model that blew straight through array boundaries without a worry in the world.
They can be useful at work, especially for tech I know little about, and as an additional set of eyes to avoid easy mistakes like off by ones, or doing wrong pointer arithmetic, but they are pretty abysmal at code generation.
Nononono “tech you know little about” means you don’t know enough to see the holes it’s making
True, but what I mean is that it can find ways to do what I need to do even for things that I don’t know a lot about. If the “solution” it finds ends up being a bunch of hacks I change my approach. If it finds supported and documented APIs, I read their documentation and make sure that my mental model of the the things I’ve just learned about matches the code and explanation from the llm, and if they do I rewrite the code in a way that makes sense and iterate from there.
I also don’t copy paste the code and rewrite it inline. I rewrite it in a different window from scratch. The llm is confined to its browser window.
Essentially, I use these things the way I used to use google a few years ago: searching for documentation and examples. That is no longer possible with today’s search engines.
I thought the same earlier this year. Opus 4.8 mostly produced garbage code in my eyes. Then Opus 5.5 came and now it can routinely produce about the same quality as me but much faster.