But I don't enjoy reviewing AI-generated PRs. Poring over hundreds of lines of overly-defensive, badly-commented, subtly incorrect code is not fun.
Ain't that the truth. There's no "because" there. A field in the middle of a struct is missing initialization? Whoops! Bitfield indexes start at 1 when bits 0 and 1 are explicitly noted in the docs as "reserved"? Whoops! A whole struct representing one of many items (the other structs are all there!) and it's supporting parsing and init functions doesn't appear? Whooops! My python-programmer co-worker makes pretty consistent mistakes when dealing with Go map types, but LLMs don't have any reason for their behavior. No "because" at all.
Comments
But I don't enjoy reviewing AI-generated PRs. Poring over hundreds of lines of overly-defensive, badly-commented, subtly incorrect code is not fun.
Ain't that the truth. There's no "because" there. A field in the middle of a struct is missing initialization? Whoops! Bitfield indexes start at 1 when bits 0 and 1 are explicitly noted in the docs as "reserved"? Whoops! A whole struct representing one of many items (the other structs are all there!) and it's supporting parsing and init functions doesn't appear? Whooops! My python-programmer co-worker makes pretty consistent mistakes when dealing with Go map types, but LLMs don't have any reason for their behavior. No "because" at all.