Remix.run Logo
▲ scottLobster an hour ago

I ran into a similar issue with Gemini 3.8 in an even simpler context. Spent several hours asking it why my new module wasn't working and each time after several minutes of thinking it would exclaim "I FOUND THE ROOT CAUSE!" and despite implementing its fix the problem would still persist.

After about a dozen failed iterations I reverted to the last known working commit (albeit with the new module only partially implemented), isolated the issue as best I could, then asked Gemini again and this time it correctly identified a latent timing bug that was the cause of all the problems.

In short, I had to manually reduce the complexity of the problem for this magic infinity-dimensional-processor to deduce what the problem was. Maybe it would have gotten there eventually, but without AI I would have just reverted the commit a lot sooner and likely figured it out on my own with some basic debug logging.

It's still a net gain, as it's successfully one-shotted coding errors and bugs that might have taken me hours to find before, but it can miss basic problems as well.

▲husseinhb an hour ago | parent [-]

That's great you find the root cause, as a way that i using it that helped me a lot which is first of all understand what is the bug without touching the code.

Then after i understand it i can make a targeted investigations for that issue and after that it will be obvious for the AI, and all of those we still didn't change even one line in the code.

After that, we fix that issue (which is the root of the cause), release and congratulation the bug was fixed this way works even in lowest powerful models.