←back to thread

Using LLMs at Oxide

(rfd.shared.oxide.computer)
694 points steveklabnik | 1 comments | 07 Dec 25 01:17 UTC | HN request time: 0s | source
Show context
forrestthewoods ◴[07 Dec 25 02:56 UTC] No.46178758[source]▶
> When debugging a vexing problem one has little to lose by using an LLM — but perhaps also little to gain.

This probably doesn't give them enough credit. If you can feed an LLM a list of crash dumps it can do a remarkable job producing both analyses and fixes. And I don't mean just for super obvious crashes. I was most impressed with a deadlock where numerous engineers and tried and failed to understand exactly how to fix it.

replies(2): >>46179194 #>>46181931 #
1. throwdbaaway ◴[07 Dec 25 14:33 UTC] No.46181931[source]▶
After the latest production issue, I have a feeling that opus-4.5 and gpt-5.1-codex-max are perhaps better than me at debugging. Indeed my role was relegated to combing through the logs, finding the abnormal / suspicious ones, and feeding those to the models.