|
|
|
|
|
|
by BoxedEmpathy
37 days ago
|
|
|
What tools are you using? What settings? What process? What's your code review like? I think this varies a lot. I find with a c++ project I'm working on that the LLM needs a lot of guardrails and guidance, and still gets a lot wrong. But with a vite/js project it often one shots complex and intricate changes in large codebases. |
|
|
Datadog + Python with a little AWS
It does better at writing code but diagnosing bugs and performance issues is a bit of a crapshoot. It's decent at diagnosing but when tasked with improving performance it gets a bit sketchy. It'll write something that runs but often times it either has subtle functionality changes or mediocre improvements
Other times I'll repeatedly have to push it to find the root cause. It'll say "hey this downstream service threw an exception that propagated as a 500" and I'll have to remind it that's a first party service with info available in the trace and source code also available that it needs to continue investigating.