5 ms·
The problem in this case is that LLMs are bad with golang, I don't write go, I am guessing from my experience with kotlin. I mainly use kotlin (rest apis) and L
by stanac 1y ago
The problem in this case is that LLMs are bad with golang, I don't write go, I am guessing from my experience with kotlin. I mainly use kotlin (rest apis) and LLMs are often bad at writing it. They e.g. confuse mockk and mockito functions and then agent spiral into a never ending loop of guessing what's wrong and trying to fix it in 5 different ways. Instead I use only chat, validate every output and point out errors they introduce.
On the other hand colleagues working with react and next have better experience with agents.
- weitendorf 1y agoBecause golang is so verbose LLMs are still extremely useful at using it without feeling like you're doing data entry or working as a typist. Converting JSON to a properly typed Go struct or doing the 3-5 things required to create+specify+send+deserialize/parse an HTTP request (with explicit error handling) is about 20x faster when I make an LLM do it, and it makes it so I don't dread or avoid those kinds of tasks.