Hacker News new | ask | show | jobs
by phoughton 60 days ago
I find describing the problem often works well, as opposed specifying a solution / change. And if it has a means to validate it's results then its significantly better as well.

So maybe describe the problem and work first on a means to detect errors, second - then let it rip.

1 comments

This. And when possible, first asking the AI to add more granular logging around the code where the problem is - then re-run the code and feed the new log in a new context.

I've used this to debug some moderately complex bugs in golang and godot code and it works really well - the combo of having a new context with the (sometimes overly) granular debug logging and only the required, specific source code.