Tech Radar

Norway is doing something that feels almost heresy in the current AI gold rush. While every other government is scrambling to figure out how to integrate LLMs into the classroom, they're stepping back. They've decided that the rush to automate thought is a bad bet, and they're pivoting toward protecting the cognitive skills that LLMs tend to replace. It's a gutsy move. Most of us are treating AI as a productivity hack, but there's a real risk that we're just outsourcing the "struggle" part of learning. If you don't have to wrestle with a difficult sentence or a math problem because a bot can give you the answer in two seconds, you aren't actually learning. You're just learning how to prompt. I'm not saying we should ban the tech, but the Norwegian approach suggests that some things are worth doing the hard way. It raises a question we've mostly ignored: what happens to a generation of students who've never had to think ...

Hyundai isn't just buying a robotics company. They're betting that the future of logistics is mobile, autonomous, and humanoid. By picking up a 65% stake in Boston Dynamics for $325 million, they've finally moved from being a curious investor to owning the whole thing. The timing is a bit too convenient to be accidental. Boston Dynamics is finally pushing Atlas into commercial deployment, and the humanoid race is getting crowded. Tesla's Optimus and Figure AI are no longer just research projects, they're actual competitors. It's a massive gamble. Humanoids are notoriously difficult to scale, and the gap between a viral YouTube video of a robot doing a backflip and a robot that can actually move crates in a warehouse is huge. I wonder if Hyundai is buying the tech or just buying the hype. The Shift from Cars to Robotics The pivot to robotics-as-a-service is a move to stop treating autonomous driving as a niche car feature and start treating it as a ge...

I found 10,000 repositories on GitHub that distribute Trojan malware. They aren't forks of a single malicious project, and they aren't all coming from one bad actor. They're spread across different contributors with different names, all just sitting there in plain sight. I stumbled into this by accident. I have a project on GitHub and wanted to see if search engines had indexed it, so I typed the project name into Google. My repository showed up in the results, but it was surrounded by a weird pattern of others that looked almost identical in structure but served a completely different purpose. It's a clever play on trust. We tend to treat GitHub as a safe harbor for code, but these repos use that reputation to trick developers into downloading payloads. I spent some time digging through the data to see how deep the hole goes. The results are honestly a bit unsettling. The scale of the infection The campaign hit 10,000 repositories. The attackers didn't ...

Switzerland is finally admitting that its decades-long moratorium on nuclear power might have been a mistake. For years, the strategy was simple: move away from the atom. But the reality of a fragile grid and the pressure of energy security are forcing a quiet, pragmatic reversal. It's a classic case of policy meeting physics. I find it interesting that this shift is happening now. We've spent the last few years talking about a total transition to renewables, but the Swiss are realizing that wind and solar can't always keep the lights on when the temperature drops. They aren't rushing back in with blind optimism, but they are acknowledging that baseline power matters more than political purity. The question is whether they can actually build new capacity fast enough to matter. Nuclear projects are notorious for sliding timelines and ballooning budgets. Can Switzerland actually pull this off without spending the next twenty years in a construction stalemate? T...

The most ambitious aerospace company in history isn't buying a launch provider. It's buying the interface where its software is written. When SpaceX acquires a tool like Cursor or a similar AI-native IDE, they aren't just adding a line item to their procurement list. They're attempting to own the actual cognitive process of how their engineers build flight software. I've seen plenty of vertical integration in my time, but this is different. Usually, companies buy the factory or the raw materials. Buying the editor is an attempt to optimize the loop between a developer's thought and the machine's execution. It's a bold move, but it's also a bit weird. There's a fine line between "optimizing the workflow" and creating a proprietary black box that makes it impossible for any one engineer to actually understand the system. The real question is whether this actually speeds up the cadence of launches, or if it just creates a massive depen...

Local models used to be toys. They were slow, a pain to set up, and generally useless for anything beyond basic text completion. For a long time, the gap between a home-run model and a frontier API wasn't just a distance, it was a wall. I remember thinking that local LLMs were essentially a hobby for people who liked tinkering more than actually getting work done. That changed for me with GPT-OSS, but the recent Gemma 4 releases are where things actually get interesting. I've been using the 26b implementation in LM Studio, and for the first time, agentic coding loops actually work. I'm seeing about 75% of the accuracy and speed I get from the top-tier frontier models. It's not a perfect replacement, but it's close enough that I've stopped reaching for the cloud for most of my development questions. I've started treating my local setup as a personalized, lightning-fast version of Google. It's particularly useful for the grunt work that doesn'...

Fake job offers are the perfect delivery vehicle for malware. They don't rely on some obvious "Urgent: Your Account is Locked" scare tactic. Instead, they target your professional ambition and the basic trust you have in someone who says they want to pay you a lot of money to solve a hard problem. Last week, I got a LinkedIn message from a recruiter at a small crypto startup. We chatted for a few days. She described a broken proof-of-concept they needed a lead engineer for, which sounded exactly like the kind of mess I enjoy cleaning up. Then she sent me a public GitHub repo to review. I didn't clone it to my machine. I've seen this movie before. Instead, I spun up a throwaway VPS on Hetzner and pointed Pi at it in read-only mode, using only file-reading tools. It turns out the "broken proof-of-concept" was actually a very clever trap. The Social Engineering Hook Attackers don't start with malware; they start with a persona. They build L...

Peer-to-peer networking usually feels like a tax you pay in engineering hours. If you want to move data without a central server, you're suddenly dealing with NAT traversal, DHTs, and the general nightmare of figuring out why two computers can't see each other. It's a lot of overhead for something that should be simple. Iroh handles this by treating decentralized data transfer like a standard API. It doesn't pretend the complexity isn't there, but it hides it behind an interface that actually makes sense. I've spent enough time with P2P stacks to know that the "magic" usually breaks the moment you hit a restrictive firewall, but Iroh's approach to connectivity feels different. The real question is whether this abstraction actually holds up when you're scaling beyond a few nodes. It's one thing to move a file between two laptops on the same Wi-Fi, but it's another to maintain that performance across a fragmented network. The P...

We've spent the last few years rushing toward proprietary formats and interactive PDFs, pretending that "rich media" is what makes a document better. It isn't. Most of the time, it just makes a file harder to open and impossible to read on a phone. We've forgotten that a reflowable, open standard is actually what a reader wants. I've spent a lot of time fighting with fixed-layout documents. There is nothing more frustrating than pinching and zooming on a mobile screen just to read a single paragraph of text. It's a lazy way to handle design that puts the burden on the user instead of the author. The industry seems to think that adding a few embedded videos or fancy animations justifies locking content into a closed ecosystem. But the real win isn't in the bells and whistles. It's in the ability for text to adapt to whatever screen it happens to be on. The question is why we're moving backward when the tools to do this right already ex...

Most people think becoming a billionaire is about working harder than everyone else or having a better idea. It isn't. I've watched enough cycles of boom and bust to know that raw effort is just the baseline. The real path to that kind of money is usually a mix of timing, extreme risk tolerance, and knowing exactly which levers to pull in a system that's already tilted in your favor. Since this is apparently the future prime ministers' club, I think it's time we talk about how this actually happens. It's a specific kind of alchemy that politicians often misunderstand, usually because they're too busy talking about "innovation" to look at the actual mechanics of wealth accumulation. Whether you're planning to run a country or you're just curious about how the game is rigged, the logic is the same. There are a few specific patterns that repeat every single time someone hits ten figures. Technical Overview The core of the system is...

The U.S. Department of Commerce just decided that "noise infusion" is out. Last week, they issued an order banning the practice for all statistical products coming out of the Census Bureau and the Bureau of Economic Analysis. For anyone who cares about how we protect sensitive data, this is a weird move. The goal of disclosure avoidance is simple. You have a secret dataset full of private information, and you want to publish a set of numbers based on that data without accidentally doxxing the people in it. For years, the gold standard has been adding mathematical noise to the results. It's a way to keep the statistics useful while ensuring no one can reverse engineer the original records. Now, the government is stepping away from that. We're left with older, clunkier methods like swapping records or just refusing to publish any count below five. These aren't just different tools. They're fundamentally different ways of thinking about privacy. The que...

The US government just pulled the plug on foreign access to Fable 5 and Mythos 5. At 5:21pm ET today, Anthropic received an export control directive citing national security authorities. The move is blunt. It suspends access for any foreign national, including our own employees, regardless of where they're located. The weirdest part is that the government didn't actually explain why. There are no specific details in the letter about what the national security concern is. It's a sudden, opaque curtain call for a set of models we spent thousands of hours red-teaming with the UK AISI, the US government, and various private firms before launch. We did the work. We invited the regulators in. We spent weeks trying to break the safeguards so we could fix them. Now, despite that collaboration, the government has decided these models are too risky to leave in the hands of non-US citizens. It makes you wonder what exactly they found during those red-teaming sessions that shi...

The only way to get a human to actually listen to you now is to prove you spent time on the request. We're drowning in AI-generated noise. When a teammate sends over a block of code or a debug summary, the first thing most of us do is scan for the tells of a LLM. If it looks like a raw prompt output, we subconsciously value it less. It's a weird new etiquette problem. On one hand, an AI that has deep access to our internal codebase and docs can produce something genuinely useful in seconds. It's efficient. But forwarding that raw output to a colleague feels like a shortcut that signals a lack of effort. We've reached a point where the quality of the answer matters less than the perceived work that went into it. So, where do we draw the line between being productive and being lazy? The Signal-to-Noise Crisis LLMs have made the cost of generating "perfect" communication zero. When everyone can produce a polished, professional email in two seconds, th...

For years, installing a third-party tap in Homebrew was essentially a leap of faith. You were trusting that the maintainer wasn't hiding a malicious Ruby script in their repository, because once you added that tap, Homebrew would happily execute that code on your machine. It's a massive security blind spot that's always felt a bit reckless, especially for anyone managing a production environment. The latest update finally fixes this with a new tap trust mechanism. Now, Homebrew won't just blindly evaluate code from an untrusted tap. It flags them first and requires you to explicitly trust the source before anything runs. It's a sensible change, and honestly, it's overdue. There is plenty of other stuff in this release, like sandboxing on Linux and initial support for macOS 15. But the real story is how Homebrew is finally tightening the screws on how it handles external code. I'm curious if this will actually change how people manage their taps, or ...