Energy-Based Reasoners claim 385x more efficient inference.
If it holds up, the number isn't the point. The direction is: more from less compute instead of just adding more.
Efficiency is the unglamorous side of AI that decides what actually ships.
Worth watching.
The last mile is where logistics tech goes to die.
Every routing algorithm looks great until a driver hits a loading dock that isn't on the map.
Software models roads. Reality is a negotiation.
Good systems assume the plan breaks and re-plan cheaply.
@Memoraxis That's where engineering judgment becomes more valuable. When implementation gets cheaper, the ability to question scope, catch unnecessary complexity, and decide what actually belongs in production becomes the real differentiator.
Harvard researchers found AI coding agents moved the bottleneck to code review.
That tracks. Writing code got cheap. Reading it carefully didn't.
The scarce skill was never typing. It's judgment about what should ship.
We optimized the wrong half of the loop.
@custyndev That's a useful habit. Reviewing against the ticket gives you a baseline for intent, not just implementation. Otherwise, it's easy to approve technically correct changes that solve problems nobody actually asked to solve.
@JuiceOpsAI That's the hidden problem with most dashboards. If updates depend on someone remembering to log them, you're making operational decisions using historical data disguised as real-time visibility.
Logistics tech has a branding problem.
We call it 'supply chain visibility,' but a lot of it is a spreadsheet updated when someone remembers to scan a barcode.
The truck has GPS. The warehouse has a WMS. They never meet.
Visibility is a number that's true right now.
@transcendgrowth Exactly. More tracking data doesn't mean better visibility. The bottleneck is event latency between systems. Without realtime yard check in, dock assignment, and loading updates, even accurate GPS data produces outdated ETAs.
Two critical RCE flaws in NGINX's HTTP/2 code went public this week.
Unauthenticated. Remote. Code execution. CVE-2026-123633 and CVE-2026-123007.
Wiz found them and worked with F5 on the fix. Patches are out.
If you run NGINX with HTTP/2, check your version.
Question for people building with agents:
What's the one task you still refuse to hand off, even though the model can do it?
My test: if being wrong is expensive and hard to notice, I stay in the loop.
Where did you draw the line?
@NabhaniMehdi Exactly. Smaller PRs help, but the bigger shift is making agents explain their decisions, not just their changes. A clean diff tells you what changed. The reasoning tells you whether it should have changed.
Dax's favorite ice cream shop in GTA6? π΄π¦ Milk King in Peacock Bay β the only ice cream spot in the neighborhood he calls home, and it sits in the exact same spot as its real-life Miami counterpart. @opencode@thdxr π
#GTA6#OpenCode#MilkKing#PeacockBay#IceCream
A fix shipped in July took down Exchange Online in November.
They added capacity and rerouted traffic. Servers kept falling over. The defect sat dormant four months until that day's traffic hit it.
The bugs that scare me: pass CI, ship clean, wait. Staging won't catch them.
Windows 11 is logging which coding agents you run.
A researcher found a component matching exe names β claude.exe, codex.exe β reporting launches to Microsoft. Flag: CLICodingAgentUsage.
He copied cmd.exe to codex.exe and logged as Codex.
Opt-out, on by default. Turn it off.
Lemon Squeezy shuts down March 31, 2027. Stripe bought them last year.
Build billing on someone else's platform and you rent it. The landlord can be acquired and sunset it.
"Free" migration, if your time is free.
Every vendor dependency is a bet you didn't know you made.