Fable Broke My App and Couldn't Fix It

I'm not going to lie, I'm pretty excited to film this video because we're actually talking about one of my old favorite topics again, performance in the web. Yes, really no clickbait. We're actually going to dive into some performance stuff. But the reason we're doing it is probably why you guys are here. Because the fixes that I'm working

on here are things that I could not get any of the models to do. But more importantly, the things that were broken here were broken because of those very same models. As great as AI developer tools have gotten and as powerful as models like GPT56 and Fable are, there are still things they don't understand.

Some of that is because these things are just really hard to get right. But some of it's because the tooling just isn't there for the agents to figure stuff out properly. And while the agents couldn't solve this problem themselves, I actually found really useful ways to wield agentic coding while I solve problems that the agents just could not

understand. What are those problems, though? Well, here I'll show you. You've probably seen the app before. It's right here. T3 code. So, what am I talking about with that? It looks like it's running fine. Everything when you click it loads immediately. It's pretty good. Well, here's the problem. My GPU process is currently using as much as 13 to 15%

of my CPU, and I'm running at 720p right now. When I blew this up to my full resolution on my laptop or even pulled it up on my 5K Studio Display XDR, this would take up to 50% CPU utilization on the graphics process. That's not good. I don't know about you guys, but this

doesn't look like a complex 3D game to me. This looks like a very simple web app. It should not be performing that poorly. Did I screw up the React code? Am I hitting the network too aggressively? What could I possibly be doing that is causing my laptop to heat up and is causing my GPU process to use