I'm hanging in there with it. The article was remarkably dispassionate about something that gets everyone all hot around here: easy stuff benefits from it a lot more than hard stuff. If your whole world is Node.js? Yeah, not a lot of deep water energy discovery geology data mining at exabyte scale or whatever. It pushed the barrier to entry on making a website with a Supabase backend from whatever it was to nearly zero. And I want to be really clear that frontend work is some of my favorite work: I love doing the web interface, it's visual and interactive and there's an immediacy that's addictive, the compiler toolchains are super cool, it's great stuff. I worked on a web browser, got some patents for it. I like this stuff.

But getting extreme concurrency outcomes or exotic hardware outcomes or low latency stuff or heavy numerics or a million other things? It's harder, the bots aren't as good. This is the divide: it can one shot a web page, even the older ones can just smoke a tailwind theme, headshot. A kernel patch to speed up a path on my bare metal box in a latency contest? Nah, not really.

But I see a lot of promise in the technology even if the sort of hype narrative around it seems pretty much false at this point: I still use the LLMs a lot. Part of that is that search just doesn't work anymore (although... Yandex got a lot better recently out of the blue of all things), and part of it is that I see enough exciting glimpses of like, if I got it hooked up to the right programming language and loaded the context right, wow, once in a while it just slams and it's kinda rare but frequent enough that I'm really interested in figuring out how to reproduce it reliably. And I think I'm getting better outcomes a little bit at a time, getting it dialed in. Two or three months ago an even with claude code would have me yelling at the monitor, now it's like, haha, i see you.