735
Say it ain't so (media.piefed.social)
you are viewing a single comment's thread
view the rest of the comments
[-] JackbyDev@programming.dev 25 points 1 month ago

Have I misunderstood the term vibe coder? I thought it meant people who weren't good at coding. I thought Stark's whole thing was that he's a genius. Is he notoriously bad at software but good with hardware or something?

[-] lime@feddit.nu 77 points 1 month ago

vibe coding is when you let an llm write almost all your code, taking its output at face value. tony stark in the films just vaguely describes to his computer what he wants and trusts that it does the right thing.

[-] d00phy@lemmy.world 53 points 1 month ago

I think the underlying understanding is that Tony wrote the AI he’s asking to write the code. So, in effect, the AI he built is a form of scripting. Rather than spending his time churning out code, the AI will churn out code that’s up to his standard because he wrote the AI.

[-] spacecadet@lemm.ee 22 points 1 month ago

This was my understanding, too. Dude created his own hardware and software and then hand rolled an AI so he had more time to spend saving the world instead of hunched over a laptop. Anything he tells his own AI to do would probably be trivial to him to write himself but would take us months.

[-] alezyn@lemm.ee 32 points 1 month ago* (last edited 1 month ago)

From my understanding a vibe coder is someone who builds software using mainly AI generated code. It doesn’t necessarily mean they’re a bad coder, but often the code generated by AI is just hard to process at this scale and people will have no clue what exactly is going on in their project.

[-] vrighter@discuss.tchncs.de 19 points 1 month ago

if they build software using mainly ai generated code, then they are a bad coder

[-] Photuris@lemmy.ml 15 points 1 month ago

I’ve tried this on personal projects, but not work projects.

My verdict:

  1. To be a good vibe coder, one must first be a good coder.

  2. Vibe coding is faster to draft up and POC, longer to debug and polish. Not as much time savings as one might think.

[-] vrighter@discuss.tchncs.de 13 points 1 month ago

exactly, you can only really verify the code if you were capable of writing it in the first place.

And it's an old well known fact that reading code is much harder than writing it.

[-] ulterno@programming.dev 10 points 1 month ago

An irrelevant but interesting take is that this applies as an analogue to a lot of stuff in electronics related space.

  • It is harder to receive data than to transmit it, because you need to do things like:
    • match your receiver's frequency with that of the transmission (which might be minutely different from the agreed upon frequency), to understand it
    • know how long the data will be, before feeding into digital variables, or you might combine multiple messages or leave out some stuff without realising
  • this gets even harder when it is wireless, because now, you have noise, which is often, valid communication among other devices

Getting back to code, you now need to get in the same "wavelength" as the one who wrote the code, at the time they wrote the code.

[-] vrighter@discuss.tchncs.de 3 points 1 month ago

i like the analogy

[-] brygphilomena@lemmy.dbzer0.com 3 points 1 month ago

I weirdly love reading code and figuring out what it's doing. Debugging is cathartic.

It might take a while and I might be cussing up a storm saying, wtf is this shit? Why the fuck would you do it this way? Why the fuck did you make this convoluted for no reason?

Right now it's unfucking some vibe coded bs where instead of just fixing an API to get the info we needed accurately, it's trying to infer it from other data. Like, there is a super direct and simple route, but instead there are hundreds of lines to work around hitting the wrong endpoint and getting data missing the details we need.

Plus letting the vibe add so much that is literally never used, was never needed, and on top of that returns incorrect information.

[-] vrighter@discuss.tchncs.de 3 points 1 month ago

enjoying it is a different issue. You probably enjoy it because it's more difficult, which is perfectly valid reasoning

[-] anotherandrew@lemmy.mixdown.ca 2 points 1 month ago

Exactly how I feel about it as well.

[-] Kbobabob@lemmy.world 6 points 1 month ago

Even if you're the one that built, programmed, and trained the AI when nothing else like it existed?

[-] vrighter@discuss.tchncs.de -1 points 1 month ago

So? Some of the people pushing out ai slop would be perfectly capable of writing their own llm out of widely available free tools. Contrary to popular belief, they are not complex pieces of software, just extremely data hungry. Does not mean they magically understand the code output by the llm when it spits out something.

[-] Honytawk@feddit.nl 6 points 1 month ago

Stark would have developed their own way of training their AI. It wouldn't be an LLM in the first place.

[-] vrighter@discuss.tchncs.de 0 points 1 month ago

and he stil wouldn't understand its output. Because as we clearly see, he doesn't even try to look at it.

[-] ulterno@programming.dev 1 points 1 month ago* (last edited 1 month ago)

What if it were just a really big Expert system?

That's usually the thing that you call AI players or COM players in computer games.

[-] vrighter@discuss.tchncs.de 1 points 1 month ago

given that expert systems are pretty much just a big ball of if-then statements, then he might be considered to have written the app. Just with way more extra steps.

[-] MaggiWuerze@feddit.org 3 points 1 month ago

Even if they build the AI doing it from scratch, all by themselves?

[-] vrighter@discuss.tchncs.de -5 points 1 month ago

yes. Because that would still mean they didn't code the app.

"killing is bad!" "but what if the murderer 3d printed his own gun?"

[-] Honytawk@feddit.nl 3 points 1 month ago

More like: "killing is bad" "but what if the 'murderer' designed, build and produced their own target?"

You can't kill a robot, so it isn't killing.

[-] vrighter@discuss.tchncs.de 1 points 1 month ago

the "target" is to get useful software out. The ai is the tool. In this example, the ai is the gun. It is the tool used to achieve the goal.

Anyone can make an improvised hammer. Stick a rock or a piece of metal on a stick. But that doesn't make them carpenters, even though they made their own tools.

[-] wewbull@feddit.uk 12 points 1 month ago

Javis, his AI assistant, did all the work.

[-] iglou@programming.dev 8 points 1 month ago* (last edited 1 month ago)

Except that he made Jarvis. Meaning he understands perfectly his tool's abilities and limitations... Which vibe coders don't.

[-] Tattorack@lemmy.world 4 points 1 month ago

Yes, but he also programmed Jarvis... So...

[-] JackbyDev@programming.dev 3 points 1 month ago* (last edited 1 month ago)

I feel like you're really forgetting the lore. Do you not remember the iconic "TONY STARK WAS ABLE TO BULD THIS IN A CAVE. WITH A BIX OF SCRAPS." He built a compact arc reactor in a cave. The other man's reply as to why he couldn't do it in a lab with more scientists and equipment was "I'm not Tony Stark."

https://youtu.be/9foB2z_OVHc

this post was submitted on 22 May 2025
735 points (95.5% liked)

Programmer Humor

25059 readers
640 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS