I’m still a fan of the theory that the only thing he was good at was creating was ai
You mean the one that turned into Ultron?
But he wasn’t. At least in the movie version, he and Banner had failed a few times, maybe more we didn’t see on screen. Something happened when Tony wasn’t there that sparked Ultron to become aware and catch Jarvis off guard. I’d give him credit for getting it 99% of the way there, same with Vision, but he didn’t make that final jump, it happened on its own.
And Jarvis wasn’t AGI. Seems like it to us, but since Ultron was apparently the big moment of A(G)I in the MCU even with Jarvis being around all that time, he was just a very flexible and even self-aware scripting that would never do something on his own accord, only following Tony’s orders. I think even Ultron catches on to that in the brilliant few seconds of waking and realization with his “why do you call him Sir?”
In the MCU yea that tracks.
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?
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.
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.
if they build software using mainly ai generated code, then they are a bad coder
deleted by creator
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.
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.
i like the analogy
- It is harder to receive data than to transmit it, because you need to do things like:
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.
enjoying it is a different issue. You probably enjoy it because it’s more difficult, which is perfectly valid reasoning
Exactly how I feel about it as well.
Even if they build the AI doing it from scratch, all by themselves?
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?”
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.
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.
deleted by creator
Javis, his AI assistant, did all the work.
Except that he made Jarvis. Meaning he understands perfectly his tool’s abilities and limitations… Which vibe coders don’t.
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.”
The more we talk about things the greater chance it becomes the norm. What’s this tony? Never heard of him. Vibe coding? Never heard of it and I don’t think I would be interested. Moving on.
