Same, I had that for a while.

The wifi names were "Surveillance Van 5" and "Surveillance Van 24" for 5Ghz and 2.4GHz channel. I set the family's cell phones network device names "Surveillance Operator 1", "Surveillance Operator 2", "Surveillance Operator 3", and "Surveillance Operator 4". For house guests sometimes it got a chuckle, "connect to surveillance van 24". I know when I went to friends who took their networks seriously, I had someone ask about it.

I am reminded of some source code for a company-specific program that I saw in the late 1990s. I don't remember why I was perusing it, as I was in IT and absolutely not a developer. But I remember being tickled at one of the comments before a block of code. It was something like, "I have no idea why or how the following code works. But every time someone tries to change it, everything breaks, so please don't touch it."

Each state that gets money in a judgement or settlement, should use that money to make sure their public education system teaches kids how to block ads.

By 2030, I don't think anyone should be able to graduate high school in America, unless they've learned how to be ad-free (on screens under their control; obviously they won't gain superpowers to blank out billboards or the sides of buses).

It's certainly possible to translate COBOL source into another computer language of your choice, although I'm not sure LLMs are the best tool for that job. An LLM might be able to give you more readable post-translation source code, but traditional machine translation would give you post-translation source code that works correctly, which is probably more important.

Another way to phrase that would be, "This is why C code is bad, because C programmers are expected to understand the rules about how to not leak memory, but there is no mechanism to enforce that requirement".

... and to their credit, eventually some of them do figure it out, and after that they (mostly) write good C code that doesn't leak. However, that doesn't change the fact that at any given moment there are millions of unseasoned C programmers out there who haven't reached that point yet, and who are nevertheless writing leaky code which gets put into production and causes trouble; and new C programmers appear every day. It's the Eternal September problem, applied to memory management.

So either (a) we ban C programmers from pushing to production until they've had at least 5 years of experience, or (b) we find some means to flag their errors at build-time, or (c) we live with the status quo messiness indefinitely. Linux is going with Rust as their mechanism for implementing plan (b).

If you have access to a God-tier LLM that you can rely on to find every bug, I think that could work.

However, I don't think anyone in the Linux community is ready to trust LLMs to that extent just yet. Not only are they quite fallible, they are also non-deterministic -- so if you ask your favorite LLM to find the bugs in the code, and it doesn't find any, and then you feed it the exact same prompt again, it might find some on its second attempt. So how do you know when to stop re-asking?

LLMs are currently constituted are very useful for finding bugs, but not so useful for guaranteeing that no bugs remain.

You know what improves code quality? Process improvements.

You know what doesn't improve code quality? Telling people that they suck. It's pointless and immature.

They might get a better responsie by requesting $4.99/month to remove the Meta AI slop from their Facebook interface.

That's not the reason that both bombs were dropped. They were dropped because the military saw them as just another tool in the toolbox, just like the bombs dropped on all the other cities that continued to be dropped on other cities until the surrender. Truman ended the military's control of atomic bombs after Nagasaki, when the USAAF was preparing to use a third bomb, establishing civilian control of atomic weapons. Firebombing continued, though, right up to Kumagaya, Akita, and Osaka getting hit in the 24 hours prior to Hirohito taking to the airwaves.

The agreement expired in 2030. It did not authorize Iran to pursue nuclear weapons at that time. There's a difference.

The agreement was the best available at the time. Diplomacy sometimes requires taking a temporary win, and it usually means that neither side gets everything they want. The hope was that Iran would find that they would not want or need to develop nuclear weapons. If they did go down that path, there were penalties for doing so. Future negotiations were planned to modify or extend the agreement as it got closer to the expiration date.

That's how such agreements work. Every arms treaty signed between the US and USSR had an expiration date. The expiration date was not an agreement that at the end, both sides would immediately rearm. They were meant to establish a new normal and a baseline for future negotiations, and that's what happened. Over time, the arsenals were negotiated down from tens of thousands per side to a few thousand per side, with only a fraction of them deployed or even deployable. The last one expired a few months ago, but neither side is racing to add to their deployed warhead count.

There is no way to outright prevent Iran from developing a nuclear warhead without occupying the country and removing its entire current government. That is hundreds of billions of dollars, tens of thousands of lives, and an even worse look for the US than it has right now. Negotiating a deal like the JCPOA is the best option available. But every time Trump starts to talk about a deal and details start to leak out, they look a lot worse than the JCPOA. Trump is incompetent, he started a war that even Republicans are turning against, and he's arguably left Iran in a better place than it was before. Iran now knows that they can cut off the Strait of Hormuz, and no one can or will do anything about it. Worse, Trump has stated that he would be OK with Iran charging transit fees. If that starts, everyone else who controls a waterway that is otherwise internationally accessible is going to charge them, too. Indonesia and Malaysia would be the top two who could affect global trade, and while both have said that they would not, it's hard to say what future governments would do if they came under budget stress and had a precedent to point to.

...is to not collect the data in the first place.