LLMs are a massive cognito-hazard for junior devs and mid-level peeps who are susceptible to laziness and giving up agency to an agentic AI.
If AI companies weren't trying to replace software engineers on their path to creating a god, they would've noticed this a year ago and worked on special models for junior engineers to use which forces them to retain agency and learn.
Amazon is holding a mandatory meeting about AI breaking its systems. The official framing is "part of normal business." The briefing note describes a trend of incidents with "high blast radius" caused by "Gen-AI assisted changes" for which "best practices and safeguards are not yet fully established." Translation to human language: we gave AI to engineers and things keep breaking?
The response for now? Junior and mid-level engineers can no longer push AI-assisted code without a senior signing off. AWS spent 13 hours recovering after its own AI coding tool, asked to make some changes, decided instead to delete and recreate the environment (the software equivalent of fixing a leaky tap by knocking down the wall). Amazon called that an "extremely limited event" (the affected tool served customers in mainland China).
CPU designers intentionally hide instructions from the public documentation. They are called "non-standard instructions" and they exist in every modern CPU. A 2025 fuzzing tool called MystFuzz systematically hunts for these hidden opcodes to find security bugs before attackers do.
Our @NASARoman space telescope is officially slated to launch on Aug. 30!
Get the details and follow Roman's journey on our new Roman Space Telescope blog: https://t.co/72iud38kMm
Dear @JeffBezos, you're a Stargate fan aren't you? Don't you want to see this come to life? Just give them a smaller budget. I'm sure they can make it work.
I've just realized what ARM64X and imo this is the nastiest PE extension Microsoft has ever shipped
it's literally the most horrific fat binary mankind has ever invented because it contains two types of binaries one of which is a horrific hack:
- native ARM64 code with ARM64 ABI
- hybrid ARM64EC code which combines:
+ native x86_64 code
+ native ARM64 code gated with special relocation types, using a different ABI that mimics the Windows x86_64 one
PSA: @TencentGlobal is aggressively scraping the Internet to build yet another AI slop chatbot, DDoSing many websites in the process.
We've found that, as of last week, their scraping bots can now solve Cloudflare challenges and behave like real users while ignoring robots.txt. In the last 24 hours alone, our website received more than 3 million successful requests from Tencent bot IP addresses, plus another 1 million that were blocked by Cloudflare challenges.
These recurring DDoS attacks from Tencent have been going on for over a year, and we have been constantly adjusting our firewall rules to filter them while trying not to impact Tencent's real users. Because that is no longer possible, we're now fully blocking Tencent IP addresses, starting with ASN 132203. We recommend other sysadmins do the same.
Other ASNs displaying similar abusive behaviour will also be fully blocked from our services.
We'd also like to thank @Cloudflare for sponsoring us with Project Alexandria as of 2025, giving our sysadmin the tools to keep RPCS3's online services running without service disruptions.
Just saving this here to document a story and as a self reflection on whether AI is really making me more productive
Yesterday morning I found a way to complete the new HVM approach, that is much faster than before. I spent a few hours writing a spec, and then used Opus to implement. About 3k lines of C code later, everything worked and performance was incredible: 5x faster than HVM4 (stable at ~10x now). So, in one day I had outclassed HVM4. Incredible. I'd never have implemented that so fast manually.
Now, enter today. I want to turn this into a real thing, but I haven't fully read the 3k lines yet. So, how do I trust it? I spent the whole day auditing the code. With AI. Several bugs found, most minor like forgetting to collect() some argument. But then I stumble upon this:
λ{ inl: 1 ; inr: 1 }
This was a test. But wait. This is matching on inl/inr. So the branches should receive the value of the Either. But they were numbers instead. Numbers aren't functions. This makes no sense. So why this is a test?
It then stuck me. The AI completely misunderstood how function arities work. It literally assumed for no good reason that HVM5 was supposed to handle under/over-applied functions. For no good reason. I never wrote that. It never asked either. It just kinda thought "HVM is weird in some aspects, this might be one of them..." - and then it went on to implement a massive system to handle cases that should never happen to begin with. And all of that code is obviously wrong because it should not even exist. It is wrong. It is damage. And it is there.
But it isn't too bad either. I just told Opus that it was wrong. Perhaps not so politely. And it solved it just fine.
But then this begs the question. I spent ~20 hours in this file, and it is STILL not done. I went from 0 to 95% in the first 5 hours. Yet, 15 hours later, it is still not 100%. I suppose that is the real effect of using AI. If I had just written the C file manually in the last two days, would I not be further than where I am *right now*?
Surely, the first version would have taken much longer to drop. But when I'd finish writing all that code, there would be zero, literally zero retarded shit. And, just today, I caught 5 or 6 retarded shit. And the worst part is: I don't know what the number of retarded shit left is, but I'm afraid it is >0.
So if I have to read it all, review it all to ensure there is no retarded shit... what did I achieve by using AI, other than that dopamine anticipation?
One paid full price for 9.9% of the company by re-appropriating a grant as a buy. The other wants to use the govt's monopoly on violence to seize 50% of the company without paying anything.
Re-appropriating grant money as a purchase was a great idea, and that should've been the plan from the start. Rare Trump W.
A researcher found critical Windows zero-days.
Reported them to Microsoft.
Microsoft denied the bug bounty.
Deleted their account.
Banned them from GitHub.
Then threatened criminal charges.
The researcher dropped six zero-days in six weeks.
Three got used in real attacks within days.
Other researchers are now handing them free vulnerabilities as a gift.
Microsoft’s Digital Crimes Unit is considering legal action.
Against the person whose bugs they refused to pay for.
This is Microsoft’s bug bounty program.
I had this idea for a 4-player dynamic splitscreen setup.
Not sure if it's better than a traditional splitscreen setup, but I like the fact that you can see the relative locations of other players visually.
Might write a blog post about this!
#godot#gamedev
@girishmallya If they were telling the truth, sure. But after hearing all this reporting about upselling, I am not so sure because I had never heard this before.
Two years ago I was 20 min late for an appointment for my Canadian visitor visa. They told me I had to rebook because the system would not let them sign me in.
They also told me I could get a fresh appointment immediately if I went to the premium lounge.
No other VFS centre has ever told me that I can't enter if I'm late.
90% of the visa trauma I had was because of VFS Global.
It’s extremely embarrassing that this company came out of India.
For almost all my visa appointments until now ( I love The Hague govt for abandoning VFS ) they would push me and all other people around to pay their premium fees for “consultation” on how to apply to a visa.
“If you don’t pay the premium fees, we won’t check your documents”
They would treat everyone so badly when all people did was stand in a queue waiting for their turn to apply for a visa.
I really hope no one has to ever go through VFS’s dark patterns.