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

Fuck AI

5446 readers
1266 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* (last edited 1 week ago) (1 children)

Uh... i copy and past the code in, after either a simple command, or a question, or something like that, then do:


code


... and then return to comments or questions or directions if I have more.

Or maybe if the code is throwing either syntax or runtime errors, give it the errors.

Then, it generates some output, with a code block, I examine it, copy and paste it back to wherever, see if it throws syntax errors, see if it runs, see if it broke something, see if new thing I'm trying to make actually works right, etc.

much more rambling thoughts of someone who hopefully does not have a form of ai psychosis

I don't even know what Codex is.

I've been writing code for decades and I... I still don't like 'get' IDEs, most of the time? They almost always seem like more trouble than they are worth.

I'm just used to much more lightweight editors, or as with the case of Godot, it has a pretty decent code editor / manager window thingy.

This is all an excercise in ... optimizing laziness, lol.

But uh yeah, Alpaca is a kind of containerized way of handling LLMs.

The whole idea is that it is self contained, sandboxed.

I am extremely hesitant... to try and like, build my own version of Copilot, that is... insanely potentially dangerous.

So yeah, there are walls between the LLM and the rest of the system, thats the point.

I could try and like, build an automated workflow, but... it makes mistakes too often, and frankly, its... basically kinda like partner coding.

I point out mistakes it makes, it points out mistakes I make.

It is a communicative collaborative process, if you're doing anything remotely conceptually complicated.

And you can just tell the thing 'do a sanity check on this code' or ... describe an idea and ask it to critique it, or ask it to ask you questions that it might have.

I basically just treat it as a fellow programmer, you know, another autist, sort of like another normie human, sort of not, lol.

Often, it will kind of... conceptually pigeon hole itself into a particular way of trying to solve a problem.

We'll spend time trying to get this to work, it doesn't, I get frustrated, engage my own actual brain for a bit, realize what it is trying to do is fundamentally nonsensical, propose a different approach.

Sometimes, nope, my idea isnt compatible, it says as much.

Sometimes it basically has a facepalm moment and says wow thats a much simpler way to do this, and then we figure it out in like the next 10 minutes.

... This is very much like real coding with other real people, at least in my experience, lol.

Brains together strong, theoretically.