I’m quite staunchly anti-LLM, but code review is where I think they are most suited. Mind you, only as PART. But their ability to hold large bodies of well-structured code in context is what gives them the edge to find possible bugs and exploits a human has overlooked.
They never should’ve been used for code creation, and in reality they’re being use on both sides of the equation going completely unmonitored or, at best, there’s a burnt out human sitting in between rubber-stamping commits because the entire pitch for this shit is to increase productivity (output) and move at a rate designed to outpace them.
In my experience, AI writes better code (and tests) than most developers and much worse architecture than a senior engineer.
I suspect the architecture is fine, really, but AI is so comfortable juggling 19 balls that it’s architecture never needs simplification and clarity. But as a human reading it, it’s just a mess and humans need much more coherence and encapsulation.
I feel like AI writes good code but then every once in a while it does the absolute dumbest thing in the world. And you have to be really vigilant so you can’t it doing dumb shit.
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.
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.
I’m quite staunchly anti-LLM, but code review is where I think they are most suited. Mind you, only as PART. But their ability to hold large bodies of well-structured code in context is what gives them the edge to find possible bugs and exploits a human has overlooked.
They never should’ve been used for code creation, and in reality they’re being use on both sides of the equation going completely unmonitored or, at best, there’s a burnt out human sitting in between rubber-stamping commits because the entire pitch for this shit is to increase productivity (output) and move at a rate designed to outpace them.
In my experience, AI writes better code (and tests) than most developers and much worse architecture than a senior engineer.
I suspect the architecture is fine, really, but AI is so comfortable juggling 19 balls that it’s architecture never needs simplification and clarity. But as a human reading it, it’s just a mess and humans need much more coherence and encapsulation.
Ever seen them do documentation? I wrote better shit in high school
I feel like AI writes good code but then every once in a while it does the absolute dumbest thing in the world. And you have to be really vigilant so you can’t it doing dumb shit.
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
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.