4 ms·

I work at a large devsec company which uses primarily Go and TypeScript I've found that the LLM generated Go has few mistakes, and generally isn't too obscure.

I work at a large devsec company which uses primarily Go and TypeScript I've found that the LLM generated Go has few mistakes, and generally isn't too obscure. But the volume of code is so high, colleagues do a bad job of reviewing it. I've seen a lot of very silly decisions made, like returning the wrong HTTP code, or miscategorizing a metric used for an SLO, that I just don't think is helped by the sheer volume of code one has to wade through. Ironically, we are considering migrating some initiatives to Rust, exactly because experiments indicate it works well with LLM development.

jeffbee 2mo ago
Isn't any equivalent system going to have more statements in Rust than it would have in Go?
- super_flanker 2mo ago
  Why would you think so? Rust provide better type system and abstraction mechanisms compared to Go, hence equivalent system should have less lines of code, at least in from my experience.
  - icedchai 2mo ago
    Considering every other line of Go is `if err != nil`, this makes sense. I do prefer Go's simplicity, personally.
- bb88 2mo ago
  Yes, and that's the case I've seen as well. I would also say rust is also more heavy on symbols, which can make code look kinda hard to parse in places. But weirdly Opus (N=1) in Claude Code does okay on it. Enough I can reliably have it write software and feel confident it works.
Cthulhu_ 2mo ago
I'd argue that this is neither down to the programming language nor LLM used, but down to your own company's requirements, testing, and code review practices - but you did point the latter out so you're aware of it. I think the only thing you realistically can try to do is slow down. But it's also a trap I fall into myself - I don't usually thoroughly review my own merge requests because I wrote them, but now that LLMs generate them I don't review my code thoroughly either, and some issues have fallen through. Nothing critical, just stuff that, if someone asked me to review it, I'd flag up as something that could be polished a bit.

jeffbee 2mo ago

Isn't any equivalent system going to have more statements in Rust than it would have in Go?

super_flanker 2mo ago
Why would you think so? Rust provide better type system and abstraction mechanisms compared to Go, hence equivalent system should have less lines of code, at least in from my experience.
- icedchai 2mo ago
  Considering every other line of Go is `if err != nil`, this makes sense. I do prefer Go's simplicity, personally.
bb88 2mo ago
Yes, and that's the case I've seen as well. I would also say rust is also more heavy on symbols, which can make code look kinda hard to parse in places. But weirdly Opus (N=1) in Claude Code does okay on it. Enough I can reliably have it write software and feel confident it works.

Cthulhu_ 2mo ago

I'd argue that this is neither down to the programming language nor LLM used, but down to your own company's requirements, testing, and code review practices - but you did point the latter out so you're aware of it. I think the only thing you realistically can try to do is slow down. But it's also a trap I fall into myself - I don't usually thoroughly review my own merge requests because I wrote them, but now that LLMs generate them I don't review my code thoroughly either, and some issues have fallen through. Nothing critical, just stuff that, if someone asked me to review it, I'd flag up as something that could be polished a bit.