Top 5 film for me. Watched it for the first time when I was in high school. This quote from Ellis towards the end of the film left a big impression on me:
"What you got, ain't nothing new. This country's hard on people. You can't stop what's coming... it ain't all waiting on you. That's vanity."
Link to the scene:
https://t.co/M5XX3tFUqo
i've been thinking about this since i first tried a waymo
someone can confidently stand in front of it and fuck with you however they want and you're just stuck
can't do this with a real driver because you don't know they won't run you over
VoidZero is joining Cloudflare.
Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite+ remain MIT-licensed. Evan and the VoidZero team will continue leading them.
Cloudflare shares our commitment to open source. Together, we can keep investing in the tooling developers rely on every day, while bringing the Vite ecosystem and Cloudflare’s platform even closer together.
Our internal data shows Claude is accelerating AI development—a possible path to recursive self-improvement, or AI autonomously building a more capable successor.
It’s happening faster than we thought, and the implications deserve greater attention. https://t.co/OVVPJO7VQx
I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem.
As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)!
I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work.
It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results?
88ms => 1.5ms
150K allocs => ~500 allocs
Incredible right? Nope.
My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path.
This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput.
The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity.
Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.
@united Already did. Nothing worked. Only successful via iOS app flow. Also your app is broken, slow, and sucks. Worst airline app I’ve used so far. Get better.
there's actually no way. what is going on? do you guys use your website?
i entered the same information in the app and the reservation was indeed found
pathetic
We’re thrilled to announce the Antigravity CLI, a lightweight way to spin up the same Antigravity agents right from the terminal. 💻
It gives you the exact same harness and same models, with a product experience tailored for the command line. It adapts entirely to you: your keybindings, your themes, your workflows.
Full Antigravity CLI Walkthrough:
Agents work well with static types, schemas, state machines, etc. Keep deterministic what should be deterministic.
Stop trying to make everything non-deterministic.
@skeptrune Dude on a flight rn and had the exact same thoughts as I was connecting to the WiFi
Couldn’t believe the process I had to go through
Like why doesn’t it just work. Why am I having to navigate this airlines specific WiFi connection interface
Can’t happen soon enough
Once you truly internalize you’re missing every shot you aren’t taking anyways, you’ll start start taking a lot more shots
What do you have to lose
Nothing fool
anyone thinking about, learning, or already working with agentic systems, you should know this.
the first few steps of your setup matter more than any model or framework you pick later. get them right and you never lose your flow.
the foundation nobody posts about:
> 1. tailscale. a private mesh network across every machine you own. laptop, desktop, rented node, all on one secure tailnet, reachable from anywhere. nothing else works well until this does.
> 2. termius, over that tailnet. one SSH client that reaches every node, phone included. you are never away from your stack.
> 3. tmux. persistent sessions. disconnect, close the laptop, come back, every session exactly where you left it. agentic work runs long, your terminal has to survive that.
> 4. a private git repo. the one i am most glad i found. it is the memory layer across all my agents, they pull, they work, they merge back, the codebase stays alive between sessions. context that would die in a chat window lives in the repo instead.
> 5. script everything from day one. ssh aliases for every node, setup scripts, the boring boilerplate automated. if you will do a thing more than twice, it is a script.
everything past these five is decorative. know these cold.
and the habit that ties it together: ask the AI itself. for the config, for the error, for any of it, let the agent do the lifting, then double check what it hands you.
lock the five, build the habit, and you make it. skip it, anon, and you ngmi.