A brand new bridge between Detroit and Canada is finished and ready to open. It would speed up traffic for millions of trucks, cut delays for American businesses, and help the auto industry that employs people in every state. There is just one problem.
Donald Trump won’t let it open.
Here is why.
The family that owns the old bridge stands to lose business when the new one opens. So in January, they gave one million dollars to a pro-Trump super PAC.
Weeks later they met with Trump’s Commerce Secretary.
He called Trump.
Hours after that, Trump announced he would block the new bridge. The opening was set for June 12. It got canceled the day before. The bridge sits there finished and empty.
Now here is the part that should make every taxpayer angry.
Canada paid for the entire bridge.
Every dollar. And the United States already owns half of it for free. Trump is holding up a bridge we got for nothing, to protect a donor who wrote him a check, while picking a fight with our closest ally and biggest trading partner.
This is corruption in plain sight.
A billionaire pays, and the President delivers. American workers and businesses pay the price.
Open the bridge. A government should work for the people, not for whoever writes the biggest check.
https://t.co/9o9Gz9UrBo
We've gone really quickly from "local models are dogshit" to "local models are good actually" (like, a 12 month window from A to B). I don't think they're actually good ENOUGH yet. We need an Opus 4.5 quality local model. When that happens, I think the world will spill over.
Opus 4.5 is/was amazing, and is more than good enough for almost all tasks still as long as you pair with a frontier-level planner/judge.
It'll still require a hugely expensive machine to run it, I'm sure, like a $5K or more laptop or mac studio. But, that's going to be pennies compared to the API costs plus all the benefits of guaranteed privacy and so on.
Introducing a new side project called Model Regression. It tests daily Claude, GPT, and Grok on various benchmark statistics to determine how well its performing and to identify model degrades over time.
@edskoudis had an idea for model testing before they conducted offensive testing to ensure the model was performing as expected, and @BlasikRandy pushed me down this road with actually going and doing it.
The main intent here is the frontier models will experience outages, issues, bugs, intentional/unintentional nerfing of the models without notice. You can't typically trust day to day activities in these models for stability, so leveraging this on your daily routine to see how well the model is performing for that day is something I'll be using everyday.
Runs every morning in my DGX sparks environment and automatically updates with how well its performing.
Enjoy!
https://t.co/1Pep6NyGoh
Also open-sourced the project, can run on your own server as well and look at the benchmarks and how they are calculated:
https://t.co/GFPigpRtUF
I had an immense privilege of taking part at a #CyCon2026 panel dedicated to the upcoming new book by the CPT trio. These are my panel preparation notes. https://t.co/ORGBQQwu2t
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.
Claude Opus 4.8 is out today. It's our strongest coding model yet: up on SWE-bench Pro (from 64.3 to 69.2) and noticeably more honest about its own work. It tells you when it's unsure and catches its own bugs instead of declaring victory early. Same price as 4.7.
You can add org-specific rules in a claude-security-guidance.md file. Drop it in your repo or distribute via MDM. The plugin enforces your policies alongside the built-in checks.
Docs:
https://t.co/OO4uwdfwkx
My whole argument regarding AI boils down to this:
>>> AI increases output much faster than it increases certainty <<<
Yes, it generates more code, more prototypes, more pull requests and more “solutions”.
But every generated line still needs ownership, review, testing, debugging and long-term maintenance by humans.
And I think the market currently underestimates how expensive that last part really is.
A reminder that Russia is waging a terrorist war on Ukraine, and a reminder that standing by and watching are the richest nations on Earth, controlling the most powerful military alliance in history, an alliance created specifically to stop Russia in Europe. Sickening.
Canada strongly condemns Russia’s launch of large-scale missile and drone attacks on civilian targets in Kyiv tonight.
For more than four years since Russia’s illegal invasion, it has greatly underestimated the courage, determination, and strength of the Ukrainian people — even as Putin’s regime has relentlessly bombed Ukrainian energy infrastructure, schools, hospitals, and homes.
We call on Russia to immediately cease these strikes and end this illegal war of aggression. They prolong human suffering and do nothing to change the fact that Russia will lose this war.
Canada will continue working closely with international partners to secure a just and lasting peace for Ukraine and Europe.
Kyiv. An absolutely horrific night.
📽 This is what a European capital looks like in the dead of night.
Five years and the so-called civilized world is still ignoring russian terror.
Le combat de l’Ukraine est le nôtre, sa lutte est notre cause, et son indépendance sera notre victoire.
Aux communautés ukrainiennes du Canada et du monde entier qui célèbrent leur culture, leur identité et leurs traditions en ce jour de la Vyshyvanka : le Canada est avec vous.
We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.
Personal update: I've joined Anthropic. I think the next few years at the frontier of LLMs will be especially formative. I am very excited to join the team here and get back to R&D. I remain deeply passionate about education and plan to resume my work on it in time.
Yesterday, Russia launched one of its largest drone and missile attacks on Ukraine in four years.
Canada unequivocally condemns these indiscriminate attacks. I express my deepest condolences to those injured and everyone mourning their loved ones.
Canada stands with Ukraine as it defends itself against this unconscionable aggression and we will work with allies to sustain pressure on Russia to bring this conflict to an end.
We’ve been ignoring the security technical debt for too long hoping the payday will never come because finding all those insecure bugs (and features) demanded far more hackers than we had. That has now changed and it’s time to face the music.