Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Some late-night vibe coding with Claude. This time I tried implementing the paper "Real-Time Ray-Traced Ambient Occlusion of Complex Scenes using Spatial Hashing" (by Pascal Gautron) using LightweightVK. The starting point was a basic working ray-traced AO demo without spatial hashing which I already had - just stochastic noise...

38,418 görüntüleme • 7 ay önce •via X (Twitter)

23 Yorum

moti profil fotoğrafı
moti7 ay önce

this is so freaking detailed and cool!

Łukasz Bogaczyński profil fotoğrafı
Łukasz Bogaczyński7 ay önce

Nice! One thing that (IIRC) wasn't mentioned in the paper was cache invalidation. Each entry stores the age that's used when doing the linear search, but do you also use this age to reject samples when reading the cache to reject possibly stale entries?

Sergey Kosarevsky profil fotoğrafı
Sergey Kosarevsky7 ay önce

There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors 😀 In my case, cache entries are retired after N frames, and I`ve found that using 2 frames strikes the best balance helping ambient occlusion converge while still allowing quick updates when the camera moves and new geometry comes into view. Claude needed quite a bit of guidance here and wasn`t able to make meaningful progress without being manually steered through different heuristics.

Łukasz Bogaczyński profil fotoğrafı
Łukasz Bogaczyński7 ay önce

Ohh, that's quite a short lived cache then, I expected more like 10-30. Actually I had the same exact idea last week. I read the paper and now I'm about to see how far can I go with Claude and implementing Doom-like GI with it. Regarding cache invalidation - check my profile bg

Sergey Kosarevsky profil fotoğrafı
Sergey Kosarevsky7 ay önce

I think the next step to improve visual quality is to introduce invisible guard bands around the camera view. That way, geometry entering the frame can pick up valid cache samples before it actually becomes visible to the user. With this in place, we could increase cache age retirement to around 5–10 frames without causing eviction stalls. Another area worth exploring is tuning the total cache size (the video above uses 10M entries).

Panos Karabelas profil fotoğrafı
Panos Karabelas7 ay önce

Very cool!

Sergey Kosarevsky profil fotoğrafı
Sergey Kosarevsky7 ay önce

Thanks, Panos! I was curious whether it is possible to prototype a demo from a graphics paper in just a few hours. Now I know!

Panos Karabelas profil fotoğrafı
Panos Karabelas7 ay önce

I think with skills and an open mind (no unjustified AI hate) some cool things are possible, that's one of them 🙂

Sergey Kosarevsky profil fotoğrafı
Sergey Kosarevsky7 ay önce

This was very much vibe-coded. I didn`t touch the code directly. Instead, I guided Claude and then, at the end, just hardcoded a few parameters to match my visual taste after tweaking them in the UI to find that sweet spot.

Sergey Kosarevsky profil fotoğrafı
Sergey Kosarevsky7 ay önce

I will do some Claude-assisted cleaning and optimization passes on this code before publishing it.

Dino profil fotoğrafı
Dino7 ay önce

this is sick, love seeing actual papers implemented in real time curious how much the spatial hashing helped with perf vs the naive jittered version? always wondered if the complexity tradeoff is worth it on mobile

Sergey Kosarevsky profil fotoğrafı
Sergey Kosarevsky7 ay önce

The naive jittered version runs about 1.5x faster than the naive vibe-coded spatial hashing. That said, the naive vibe-coded spatial hashing also produces noticeably better visual quality 😀

Babzo profil fotoğrafı
Babzo7 ay önce

Impressive work! I did something similar with Peter Shirley's Raytracing in one weekend by porting it to WebGPU. My focus was in being able to learn Raytracing from scratch so I didn't use a lot of AI help

Sergey Kosarevsky profil fotoğrafı
Sergey Kosarevsky7 ay önce

I was testing how quickly I could build a prototype using Claude. Even in the best-case scenario, it would’ve taken me an entire weekend to code this unassisted myself - compared to just 4 hours in one evening.

Babzo profil fotoğrafı
Babzo7 ay önce

AI really speeds up everything and the fact that they used to be slow at shaders but that gap is closing really fast now. I haven't tried Claude but of the copilot models in Vscode , GPT 5.3 Codex is my best to use.

David Sena profil fotoğrafı
David Sena7 ay önce

Awesome stuff!!! What I would like to see now is it running at together with everything else 😉

Sergey Kosarevsky profil fotoğrafı
Sergey Kosarevsky7 ay önce

I will be yet another interesting exercise, sure!

David Sena profil fotoğrafı
David Sena7 ay önce

Meant to say ...see it running at 16ms with everything else"

Sergey Kosarevsky profil fotoğrafı
Sergey Kosarevsky7 ay önce

On my desktop PC, sure!

Vila profil fotoğrafı
Vila7 ay önce

impressive

Arete profil fotoğrafı
Arete7 ay önce

For what?

Anwar Benhamada profil fotoğrafı
Anwar Benhamada7 ay önce

This is the best kind of vibe coding writeup. You got to "visually acceptable" in 4 hours, but you're also honest that the code is messy and unoptimized. That gap between "it works" and "it's ready" is where most of the real engineering lives. Cool to see this running on mobile too.

SaberTech profil fotoğrafı
SaberTech7 ay önce

I have no idea what you said, but that looks freaking awesome. Way to go!

Benzer Videolar

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)

Ian Nuttall

195,173 görüntüleme • 1 yıl önce

CLAUDE CODE JUST SHIPPED THE FEATURE THAT SOLVES THE BIGGEST PROBLEM EVERY BUILDER HAS WITH AI AGENTS. The problem: Claude starts a task, gets distracted by a sub-problem, goes down a rabbit hole, and never finishes the original thing you asked for. The solution: /goal One command. You set the goal at the start of the session. Claude now has a north star it checks against every action it takes. Not just at the beginning. Throughout the entire session. Every time Claude is about to do something it asks: does this action move me toward the goal the user set or am I drifting? If it is drifting it corrects. If it completes a sub-task it returns to the primary goal. If it hits a blocker it reports back instead of spending 45 minutes solving the wrong problem. This sounds like a small feature. It is not. The reason most people do not trust Claude Code for long autonomous runs is not capability. It is reliability. A Claude Code session that reliably finishes what it started is worth 10 times more than one that is more capable but wanders. /goal is the feature that makes long autonomous sessions reliable. Set the goal. Let it run. Come back to a finished result. Not a result that got 70% done before Claude decided the sub-problem was more interesting. Done. The builders running overnight agent sessions are going to use this command on everything from today forward. Bookmark this. Follow CyrilXBT for every Claude Code feature the moment it ships.

CyrilXBT

19,586 görüntüleme • 5 ay önce

Day 18. Building the game I've dreamed of for 15 years with AI. I've learned how to build proper levels with AI. I take the design and the architecture, and AI helps me put it all together and check the balance. I made the first level of my game almost entirely by hand. I wanted to understand how it works and what I like, from how big the trees should be to how the textures tile. After a day digging around in the terrain tools it all made sense, and I could see how much of it could be automated by painting zones. Claude helped me a lot with the tileable textures. Matching the colors took a ton of iterations, and that was the hardest part of the whole level. For level two I took a different route. I built myself a simple HTML planner with a logical map of the level, where I place everything and design the layout. Painting a level and making it fun to play are two different jobs, so I kept the design for myself. We even made automated tests with Claude: 2D simulations that show which routes a player takes and how hard the level is. They're rough, but they give a real sense of how the level plays. Once the plan was ready, I handed everything to Claude, and 3-4 hours later I had a working level. It reused the patterns from my first level, scattered objects unevenly so nothing looks placed on a grid, and generated extra props whenever I asked. I showed it one example, it picked up what worked, and we turned that into a skill for the next levels. The video is a quick flight over level two, then how it got there, from my first sketch to the version I play now.

Stefan 3D AI

45,935 görüntüleme • 21 gün önce

Pi was built when there were already agent harnesses around. Here’s why Mario Zechner(Mario Zechner), found them suboptimal and built Pi, a minimalist self-modifying agent: #1 - Mario initially was a believer in Claude Code: "I was a believer in Claude code because they were the first that packaged agentic search up in a really compelling package. And at the time that fit my workflow really well. Everything around the LLM was kind of nice and tidy and easy to understand. I was super happy. I was proselytising Claude code." #2 - Reverse engineering Claude Code highlighted the degradation that Mario felt as a user: "I personally like simple tools that are stable and that I can rely on. Even if they have non-deterministic parts, all the deterministic parts should be as stable as possible. That was just not the experience with Claude Code around summer 2025. They would take away your control of the context. They would inject stuff behind your back, which is bad. Then, your workflows stopped working because there's now a system reminder that you don't even see in the UI that would modify the behaviour of the model. They would also do this to the system prompt. I built a little service where I can track the progression or evolution of the system, prompt and tool definitions and, with every release, it was messing with stuff. That just messed with my workflows and I don't appreciate that." #3 - PI was built with an appreciation for simple and reliable tools: "If I commit to a development tool, I want it to be a stable, reliable thing like a hammer. I don't want my hammer to break a different spot every day. That's terrible. We need somebody who goes the full velocity kind of way. But I don't want to work with a tool like that."

The Pragmatic Engineer

63,020 görüntüleme • 5 ay önce

"That pussy Adam Cole broke his ankle like the complete dork that he is." MJF talks about the revisionist history of his story with Adam Cole "Here's what happened. At the time, and this is just a fact, we were the highest minute-for-minute drawing angle, not just in AEW, but in all of professional wrestling at that point. We were moving the most merch in the company. At that point, and was to no fault, Bloodline's going to go down as one of the greatest long-term thing, but at that point there was a bit of lull in their story at that point in 2023, and we had taken lead and Better Than You, Baby is what everybody was talking about and then that pussy Adam Cole broke his ankle like the complete dork that he is and then he decided to turn on me because he's a horrible human being. But I learned a lot in that in that year I learned a lot about myself you know when I when I was out—full disclosure I was in a very dark place." I also asked about the injuries he had suffered "It was my hip, my left shoulder; my last two pay-per-view matches—pretty much the left side of my body was useless. But I wasn't going to tell the doctors that because that's not how I was brought up. In not just in real life, but in this business. When I had that time off, I had a lot of time to reflect and it made me angry. Now I look back on it and I shouldn't have been angry at the fans. Who I should have been angry was that myself. Because I went from being, ‘MJF is the best thing since sliced bread,’ and within a flip of a switch, ‘It's MJF sucks. He's killing this company that we love.’ It took, if we're being honest, it took all the way into like the first month of this year of 2025 for everybody to be like, ‘Maybe we were harsh. Maybe he's actually still one of the best in the world. They can't help it. But I know why. It's because nobody likes a braggart. But the unfortunate thing is I can't help myself. I'm just really good at my job and I can't help but talk about it."

Sean Ross Sapp of Fightful.com

36,450 görüntüleme • 10 ay önce

Anthropic CEO Dario Amodei's message to everyone using Claude or ChatGPT at home: "I won't lie to you. There are real dangers." Amodei was asked what he would say to an ordinary person using AI at home, someone like the aunt of his interviewer, Jo Ling Kent. He started by naming the mood: "Look, my message is there's a lot of fear right now." From there, he took that fear head-on with three points: the benefits are real, the dangers are real, and you should get a say in what happens next. First, the benefits: "First of all, as always, this is a great technology and it has lots of positive uses. So let's just start with that. You know, we have hundreds of millions of people using our technology every week to do wonderful things." He points to messages that land in his inbox regularly: "Every week I get an email from someone who says this, you know, I was talking to Claude and Claude diagnosed this disease that my doctors had missed. I get emails like this every week. So, let's not forget that." Then came the part he says too much of the industry wouldn't admit: "But in terms of the dangers of the technology, I won't lie to you. There are real dangers." He calls out his own industry directly: "And I think for too long the industry lied to people about the fact that this technology had risk. The idea was that they would present it as positive as [possible]. We've never done that, but too much of the industry did that." For Amodei, the fix starts with honesty and extends to the person at home: "And so it starts with telling the truth. And the truth is there are risks. Risks are real. But also, you have a say in how these risks are addressed." He explains what that looks like in practice: "We're doing the best we can to work with government to create the proper oversight of this technology to give voters and elected officials a say in how this technology is deployed. And we want to work with those folks as much as we can." His goal is for everyday users to get both the benefits and a voice in the decisions: "I want everyone to feel like they're appreciating the incredible benefits of the technology, but also they have a say in their voice and in their vote in determining how this technology is deployed." And Dario Amodei rejects the idea that AI's future belongs to a handful of people: "This isn't a decision for a few people alone. This is a decision for everyone." He's also clear about how much is riding on it: "But it is an important decision. I won't lie that the stakes aren't high."

Big Brain AI

39,223 görüntüleme • 1 ay önce