I mean, you can disagree with the sentiment (I certainly do), but there are still an awful lot of people saying it.

Yeah, absolutely not.

If you can’t understand your code, who can?

It’s not their code, and it’s not for them to understand. The endgame here is that code as we know it today is the “ASM” of tomorrow. The programming language of tomorrow is natural human-spoken language used carefully and methodically to articulate what the agent should build. At least this is the world we appear to be heading toward… quickly.

But the endgame is not here and will likely never be, because unlike ASM, LLMs are not deterministic. So what happens when you need to find the bug in the 100,000k LoC you generated in a few weeks that you've never read, and the agent can't help you ? And it happens a lot. I am not doing this myself so I can't comment, but I've heard many vibe coders commenting that a lot of the commits they do is about fixing the slop they outputted a week prior.

Personally, I keep trying OpenCode + Opus 4.6 and I don't find it that good. I mean it does an OK job, but the code is definitely less quality and at the moment I care too much about my codebase to let it grow into slop.

Further: configure reader mode as the default for the sites you’re most commonly linked to.

The “Do X in Y lines of code” thing where the Y lines of code include import statements is so, so silly.

I did the exact opposite of this in 2011 and it was the easily the most memorable 3 months of my life. Takes some planning (mostly making sure visa dates line up) but it is an incredible experience.

I believe the Atlantic requires an account to read gift links

It shouldn't, I guess there is a limit. I added a new link.

Not sure what IMSI rotation has to do with baseband vulnerabilities?

It stymies attempts to track mobile devices over multi-day periods using their IMSIs.

Trackability is definitely a vulnerability.

Right but it’s not a baseband vulnerability

Huh …?

IMSI tracking is a consequence of how baseband devices communicate over-the-air, just as WiFi MAC address tracking is a consequence of how 802.11 devices communicate over-the-air.

And it's definitely a vulnerability, because it's used to track end users and reduce their privacy.

So it IS a baseband vulnerability. And IMSI randomization mitigates it to some degree, just as WiFi and Bluetooth MAC randomization mitigate tracking via those identifiers.

I’m arguing that just because a baseband processor is involved that doesn’t mean IMSI tracking is a vulnerability of the baseband processor itself. IMSI provisioning and randomization cannot be done without cooperation with the network operator and has nothing to do with the baseband processor itself.

Well that’s a really, really easy thing to say. Curious if you’ve actually thought through how you’d go about that. If there weren’t any non-peaceful protests to participate in would you start one? How? Is it possible that it’s not that simple?

Common trend with online activists is that they clearly don't want to risk jail themselves, but they like to actively encourage others to get violent.

At a minimum! We don’t know where the coyote started from.

For all we know the Coyote could have been from Oakland or Sausalito.