Taelin@VictorTaelin
Aaand 3 hours later, it failed (obviously)
I mean that post was a joke but I honestly don't know how I could possibly solve this problem. Here's the story:
While implementing an app in Bend, GPT-5.5 found a bug: some memory was being reclaimed even though there were still pointers to it. This crashed the app, so, it went for a fix.
The solution: GPT added a *marker* for objects that *might have been wrongly reclaimed* so that it can rollback the operation later on.
This is horrible. It is just sad.
There is no scenario on which this would ever be a good idea.
Even by READING the idea you can tell it is stupid.
This behavior is the only thing preventing me from being outside, playing with the cat, instead of babysitting agents all day.
The real issue, ofc, is that a primitive function was cloning pointers without marking them as "shared". But what makes me the most upset is HOW I made the AI realize this.
It went more or less like this:
"Hey, do you understand how Bend reclaims memory?"
"Yes, ."
"Okay, and what was the bug?"
"Yes, ."
"Is that possible given your explanation?"
"No, that should never happen."
"Do you see the problem now?"
"Yes. Let me fix it."
Like. I didn't spell out the solution. I just told him that it did a bad thing, and asked it to pay more attention. It then figured and implemented the correct solution all on its own.
So, basically:
- GPT 5.5 was smart enough to find the bug
- GPT 5.5 was smart enough to understand the bug
- GPT 5.5 was smart enough to understand the system
- GPT 5.5 was smart enough to fix the bug
But it didn't by default. It just duct taped a terrible patch that would leave the project in a permanently broken state and eventually explode. Until I asked it to "do it right". And then it did. But why. Why do I need to be here watching. Why can't it do that on its own.
So close. Yet, so far...
