Using LLMs at Oxide
rfd.shared.oxide.computer
Using LLMs at Oxide
1–10 of 284 posts
Re: Using LLMs at Oxide
#2The empathy section is quite interesting
Re: Using LLMs at Oxide
#3Hmmm, I'm a bit confused of their conclusions (encouraging use) given some of the really damning caveats they point out. A tool they themselves determine to need such careful oversight probably just shouldn't be used near prod at all.
Re: Using LLMs at Oxide
#4A measured, comprehensive, and sensible take. Not surprising from Bryan. This was a nice line:
> it’s just embarrassing — it’s as if the writer is walking around with their intellectual fly open.
I think Oxide didn't include this in the RFD because they exclusively hire senior engineers, but in an organization that contains junior engineers I'd add something specific to help junior engineers understand how they should approach LLM use.
Bryan has 30+ years of challenging software (and now hardware) engineering experience. He memorably said that he's worked on and completed a "hard program" (an OS), which he defines as a program you doubt you can actually get working.
The way Bryan approaches an LLM is super different to how a 2025 junior engineer does so. That junior engineer possibly hasn't programmed without the tantalizing, even desperately tempting option to be assisted by an LLM.
Re: Using LLMs at Oxide
#5[deleted]
Re: Using LLMs at Oxide
#6Hmmm, I'm a bit confused of their conclusions (encouraging use) given some of the really damning caveats they point out. A tool they themselves determine to need such careful oversight probably just shouldn't be used near prod at all.
For the same quality and quantity output, if the cost of using LLMs + the cost of careful oversight is less than the cost of not using LLMs then the rational choice is to use them.
Naturally this doesn’t factor in things like human obsolescence, motivation and self-worth.
Re: Using LLMs at Oxide
#7Find it interesting that the section about LLM’s tells when using it for writing is absolutely littered with emdashes
Re: Using LLMs at Oxide
#8Find it interesting that the section about LLM’s tells when using it for writing is absolutely littered with emdashes
I believe Bryan is a well known em dash addict
Re: Using LLMs at Oxide
#9Find it interesting that the section about LLM’s tells when using it for writing is absolutely littered with emdashes
You can stop LLMs from using em-dashes by just telling it to "never use em-dashes". This same type of prompt engineering works to mitigate almost every sign of AI-generated writing, which is one reason why AI writing heuristics/detectors can never be fully reliable.
Re: Using LLMs at Oxide
#10I would have expected at least some consideration of public perception, given the extremely negative opinions many people hold about LLMs being trained on stolen data. Whether it's an ethical issue or a brand hazard depends on your opinions about that, but it's definitely at least one of those currently.