Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

First output looked done. Then I opened it. The bird went through the pipe like the wall was a suggestion. I stayed in the same Nex-N2.5 Pro chat and told it what the screen did. It didn’t restart the whole job. It fixed the file. Second run, collision was...

154,930 Aufrufe • vor 8 Tagen •via X (Twitter)

35 Kommentare

Profilbild von Aureus
Aureusvor 8 Tagen

Opening the first build and watching the bird clip through the pipe is the honest review. Telling the same chat what the screen did and getting a patched file is the part that matters.

Profilbild von sulaiman Waleed
sulaiman Waleedvor 8 Tagen

Bird clipped through wall. Told Nex-N2.5 Pro what happened. It fixed the file. No restart 🔥

Profilbild von Almusty
Almustyvor 8 Tagen

Fixing a literal collision flaw through a quick chat prompt instead of manually hunting down physics matrices in the script saves an incredible amount of friction.

Profilbild von Almusty
Almustyvor 8 Tagen

Most models hand over syntactically clean code that completely shatters the second it hits a runtime environment, so having an agent handle actual game loop feedback changes everything.

Profilbild von siremass
siremassvor 8 Tagen

Pushing the agent through interactive physics debugging loops is a great benchmark challenge. Did you notice any major bounding box formatting degradation or variable calculation overlaps when it patched the file logic on the fly?

Profilbild von Chelsea lovers
Chelsea loversvor 8 Tagen

Wait which model was this? Nex-N2.5 Pro? The fact it could patch instead of restarting the whole job is huge. Most just nuke it and start over.

Profilbild von Almusty
Almustyvor 8 Tagen

Staying in the same thread to feed a visual bug report straight back into the file without triggering a full reset is where agents actually start feeling like a real pair programmer.

Profilbild von CARAXCS
CARAXCSvor 8 Tagen

Most models stop when the code looks pretty. This one had to survive a tap. Same chat, describe what the screen did, fix the file, second run the wall was a wall.

Profilbild von Max
Maxvor 8 Tagen

good job bro 🫡

Profilbild von Hemtee👽
Hemtee👽vor 8 Tagen

appreciate brody

Profilbild von Yeesha🧡
Yeesha🧡vor 8 Tagen

I find this very interesting

Profilbild von Tyler Vance
Tyler Vancevor 8 Tagen

The fact that it fixed the file instead of starting over is nice.

Profilbild von The United Drip 🔰 (Fan Account)
The United Drip 🔰 (Fan Account)vor 8 Tagen

That’s the real test, getting something that actually works on the screen, not just code that looks good in the output. The ability to inspect the failure and fix the same file without starting over is seriously impressive.

Profilbild von I.T.M.H ^
I.T.M.H ^vor 8 Tagen

Syntax errors are easy convincing an AI that walls shouldn't be optional is where the real engineering starts.

Profilbild von Deboss
Debossvor 8 Tagen

Sounds like a smooth fix, glad it worked.

Profilbild von MEme
MEmevor 8 Tagen

“代码看起来正确”和“实际跑起来正确”完全是两回事。Nex-N2.5 Pro 能根据反馈直接修文件,这个体验确实值得试试。

Profilbild von SHAKIL khan sk
SHAKIL khan skvor 8 Tagen

models stop when the code looks pretty.

Profilbild von Elisha Web3CM & SecOp
Elisha Web3CM & SecOpvor 8 Tagen

They bring about testing mode

Profilbild von Tee boy
Tee boyvor 8 Tagen

gotta give nex a try too

Profilbild von Don$$
Don$$vor 8 Tagen

that’s pretty wild for a tool

Profilbild von Fuad_DeFi
Fuad_DeFivor 8 Tagen

without a full restart is the useful part.

Profilbild von Jude Ishola || BIG J 🗣
Jude Ishola || BIG J 🗣vor 8 Tagen

“The walls are just a suggestion” — that phrase really captures it. 😂 What stands out to me is how AI can now fix specific bugs based on feedback instead of forcing you to start the whole thing over. That kind of incremental iteration is where the real engineering productivity comes in. You build, test, get feedback, fix, and keep moving. Nex-N2.5 Pro seems to understand that workflow pretty well.

Profilbild von Crypto Therapy l 0% Trading fee on CoinUp
Crypto Therapy l 0% Trading fee on CoinUpvor 8 Tagen

Just in. Keep the reply on the product named in the post.

Profilbild von meerah 👠👜👗
meerah 👠👜👗vor 8 Tagen

"The bird went through the pipe like the wall was a suggestion" 😂 This is exactly it. Most models ship pretty code. Nex-N2.5 Pro debugs it when it actually runs. No restart, just fix the file and collision works on run 2. That’s real Computer Use.

Profilbild von EMIOLA𓃵 | Torium Ambassador
EMIOLA𓃵 | Torium Ambassadorvor 8 Tagen

What does this do?

Profilbild von ARIGATO
ARIGATOvor 8 Tagen

the ability to just patch the collision without nuking the whole file is the real win

Profilbild von Charlez | 💻 Builder
Charlez | 💻 Buildervor 8 Tagen

Nice one bro

Profilbild von Bambam
Bambamvor 8 Tagen

The real ones notice the quiet builders

Profilbild von SayoClips
SayoClipsvor 8 Tagen

The first run exposed the bug, but staying in the same loop and fixing the existing file is what makes the agent feel genuinely useful.

Profilbild von MJ Kayum
MJ Kayumvor 8 Tagen

thats Code looking correct and actually running correctly are two entirely different things. Nex-N2.5 Pro can directly fix files based on feedback, and this experience is definitely worth trying out

Profilbild von 𝕾𝖆𝖜
𝕾𝖆𝖜vor 8 Tagen

Real-world testing separates functional AI from demos.

Profilbild von iExquisite
iExquisitevor 8 Tagen

Solid context window 😀

Profilbild von Arpon
Arponvor 8 Tagen

The bird clipping then getting patched in chat sold me

Profilbild von Eminent
Eminentvor 8 Tagen

Nex N2.5 fixes code without restarting.

Profilbild von Mide
Midevor 8 Tagen

Amazing to see Self-testing models, you cooked on this champ

Ähnliche Videos

i watched gemma 4 12b build something genuinely impressive today, and then loop itself to death right in front of me. the full run is in the video, sped up but completely uncut, watch it to the end and you will catch the exact moment it stops building and starts looping right in the middle of the work. the task was clean, build a single file gravity simulator, n-body physics, orbits, collisions, running locally on one 3090 through an agent. and for ten minutes it was a joy to watch. it reached for a symplectic integrator on its own, the correct one, the kind that keeps orbits stable instead of spiralling out. real gravity with softening, proper orbital velocities, momentum conserved on collision. the physics was right. the thing actually worked. then on the very last step, writing a few tests to prove its own code, it fell into a loop. not a crash, a loop. it started repeating itself and would not stop. ten more minutes, thirty four thousand tokens into a single answer, the same fragments over and over, until i killed it myself. so it's not that gemma can't code. it did the hard part beautifully. it cannot finish. it cannot hold a long task together without unravelling, and finishing is the entire job in agentic work. here's the part that stings. i run this exact task, same harness, same card, on the chinese open models, qwen especially, and i never see this. they build it, they test it, they stop. every single time. google has the raw capability, you can see it sitting right there in the code, and then the model loops itself to death on a task a 27b from alibaba finishes clean. open weights, apache 2.0, so much to love on paper. i just need it to know when to stop talking.

Sudo su

39,764 Aufrufe • vor 3 Monaten

On this day, 61 years ago, Sidney J. Furie's "The Ipcress File" (1965) was released in the U.K. On the first day of shooting, director Sidney J. Furie gathered the cast and said, "This is what I think of the script." He then set it on fire. Michael Caine on the incident: "The driver picked me up for the first day of shooting and asked me if I was an actor in the movie, and if I had read Len Deighton’s book. When I told him I was the lead in it, he told me, ‘The whole thing is a load of rubbish, isn’t it?’ Then, when I arrived on set, Sidney had everyone gather around. He asked if anyone had any matches, and I smoked at that time, so I handed mine over. Sidney took the script, lit the match, looked at everyone and said, ‘Here’s what I think of this script’ and set the match to it. That was his copy of the script, so he asked if anyone had another copy to consult after he had burned his own, so I gave him mine. But it was a gesture, an illustration. It was a hell of a way to be christened into being the lead in a film." Sidney J. Furie on the reason for the movie's peculiar style: "I was very depressed always when we started shooting, thinking that it was going to be really lousy and I didn’t know what to do, so I told myself I would come up with a style of shooting that is different. I put shoulders across the screen, I shot up at things, I shot down, just to make it different, to give it ambiance. It was done out of insecurity, with a little cognac spiked in my morning coffee to give me courage." ("Sidney J. Furie: Life and Films", Daniel Kremer, 2015)

DepressedBergman

55,961 Aufrufe • vor 6 Monaten