Strange to see no mention of potential copyright violations found in LLM-generated code (e.g. LLMs reproducing code from Github verbatim without respecting the license). I would think that would be a pretty important consideration for any software development company, especially one that produces so much free software.
Using LLMs at Oxide
111–120 of 284 posts
Re: Using LLMs at Oxide
#112Earlier quoted context omitted.
DreamWeaver absolutely destroyed the code with all kinds of tags and unnecessary stuff. Especially if you used the visual editor. It was fun for brainstorming but plain notepad with clean understandable code was far far better (and with the browser compatibility issues the only option if you were going to production).
MS FrontPage also went out of its way to do the same.
I don’t particularly remember why, but “hand writing” fancy HTML and CSS used to be a flex in some circles in the 90s. A bunch of junk and stuff like fixed positioning in the source was the telltale sign they “cheated” with FrontPage or Dreamweaver lol
Re: Using LLMs at Oxide
#113Earlier quoted context omitted.
Watching my juniors constantly fight the nonsense auto completion suggestions their LLM editor of choice put in front of them, or worse watching them accept it and proceed to get entirely lost in the sauce, I’m not entirely convinced that the autocompletion part of it is the best one. Tools like Claude code with ask/plan mode seem to be better in my experience, though I absolutely do wonder about the lack of typing c…
> Watching my juniors constantly fight the nonsense auto completion suggestions their LLM editor of choice put in front of them, or worse watching them accept it and proceed to get entirely lost in the sauce, I’m not entirely convinced that the autocompletion part of it is the best one. That's not an LLM problem, they'd do the same thing 10 years ago with stack overflow: argue about which answer is best, or trust the…
Re: Using LLMs at Oxide
#114> LLM-generated writing undermines the authenticity of not just one’s writing but of the thinking behind it as well. I think this points out a key point.. but I'm not sure the right way to articulate it. A human-written comment may be worth something, but an LLM-generated is cheap/worthless. The nicest phrase capturing the thought I saw was: "I'd rather read the prompt". It's probably just as good to let an LLM gener…
They seem to be good at either spitting out something very average, or something completely insane. But something genuinely indicative of the spark of intelligence isn’t common at all. I’m happy to know that while my thoughts are likely not original, they are at least not statistically likely.
Re: Using LLMs at Oxide
#115A 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 shoul…
> That junior engineer possibly hasn't programmed without the tantalizing, even desperately tempting option to be assisted by an LLM. Years ago I had to spend many months building nothing but Models (as in MVC) for a huge data import / ingest the company I worked on was rewriting. It was just messy enough that it couldn't be automated. I almost lost my mind from the dull monotony and started even having attendance is…
Re: Using LLMs at Oxide
#116Re: Using LLMs at Oxide
#117> Ironically, LLMs are especially good at evaluating documents to assess the degree that an LLM assisted their creation Is there any evidence for this?
Re: Using LLMs at Oxide
#118Re: Using LLMs at Oxide
#119Earlier quoted context omitted.
> but I swear it built the comprehension I have today. For interns/junior engineers, the choice is: comprehension VS career. And I won't be surprised if most of them will go with career now, and comprehension.. well thanks maybe tomorrow (or never).
I don’t think that’s the dichotomy. I’ve been in charge of hiring at a few companies, and comprehension is what I look for 10 times out of 10.
Re: Using LLMs at Oxide
#120Strange to see no mention of potential copyright violations found in LLM-generated code (e.g. LLMs reproducing code from Github verbatim without respecting the license). I would think that would be a pretty important consideration for any software development company, especially one that produces so much free software.