this post was submitted on 17 Jan 2026
936 points (99.5% liked)

Fuck AI

5446 readers
1440 users here now

"We did it, Patrick! We made a technological breakthrough!"

A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.

AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] sp3ctr4l@lemmy.dbzer0.com 2 points 1 week ago (1 children)

So, I've been, in the last few hours, basically uh... distilling or refining the prompt.

Main goal was just to explictly capture more ... basically very specific rules that define like, this method is deprecated, use this one now, here is a generalized example, here's the old syntax, here's the new syntax, etc.

Keep running through scripts, keep asking it to do stuff, if it produces things with syntax errors, more or less work through why that is happening, rework or add to the prompt.

But something I did not expect to make a significant difference was to add a blurb to the top of the prompt that basically says 'be concise and non verbose unless asked to explain a concept or brainstorm a bigger picture, conceptual approach type question'.

So that resulted in it still being able to be conversational and contemplative, but when you're just feeding it code, errors, simple commands?

Well that makes it stop generating extraneous paragraphs telling you how wonderful your idea is and how happy it is to restate your request and tell your how its going to do it, etc etc.

Having it not do that actually significantly sped all this up, haha, as it... apparently devotes a lot of 'brain power' to figuring out how to write dumb fluff intros and outros.

And on a low power rig, its pretty impactful to strip out the bs.


But thats not an answer to your question lol.

I am just using the basic Qwen3 model, the 8B variant.

If you close Steam and don't have a browser with 10+ tabs open, this will work, it will run, hasn't blown up (yet).

I did have to uh, 6x the context size in the settings, that seems to be roughly optimal for ... not stalling out on actually reading the entirety of larger inputs, but also not blowing past the actual hardware limits.

So anyway, Qwen3 is a generalized model, and it actually just already understands GSScript circa roughly 4.1, seems to be when its training data set was formalized.

I started this all with something like 'tell me everything you know about modern GDScript for Godot' and it basically wrote a structured mini report, that served as an initial template to tweak update, revise.

So, my process has been:

Its now 2026, Godot 4.6 is out now (basically), this other online LLM said here are a bunch of things that have changed since 4.1, make a prompt that basically updates yourself.

As I tried to describe... Its basically a trial and error process of 'refining' or maybe 'distilling' the prompt, to get it to be comprehensive, but not too wordy, to focus it in without missing critical details.