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 8 hours ago | parent [-]

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

▲

bb88 7 hours ago | parent | next [-]

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.

▲

super_flanker 7 hours ago | parent | prev [-]

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 7 hours ago \| parent [-]
		Considering every other line of Go is `if err != nil`, this makes sense. I do prefer Go's simplicity, personally.