Does this also say something more about the "coffee nap"?

It's easy to regulate AI art the state level.

"Any job offer for a job based in California must adhere to the following AI disclosure".

"Any mortgage offered in a Californian property must satisfy the following AI disclosure"

etc.

AI regulation need not be about regulating AI innovation; it's enough merely to make sure it's applied fairly. And almost all real-world applications are indeed local.

I mean, you could very inexpensively integrate a GPS chip on there. You could put it into the firmware that the signal has a private key that encrypts said signal. It would likely get hacked eventually but by then probably not be export limited. So from a hardware perspective this isn't impossible.

So it's not impossible. But it wouldn't work because a Server GPU, inside of a rack at the bottom wouldn't get signal. You could maybe... maybe... build a big enough antenna into every GPU that it would at least pickup what continent it's on within a margin of error. So mayyyyybeeee it's possible it would still work. But probably not.

I used to work at Microsoft. My employment contract specifically called out a load of personal pre-existing projects, plus ongoing and future ones, and stipulated that MS would have no ownership nor claim. I did ask for these callouts, but they were happy to go along.

I'm a software developer. Part of AI is like if I had 200 interns working for me -- some of them smarter than me and already more knowledgeable about some areas, some of them not, none of them familiar with my team's codebase. There are real cases where I could get those 200 interns to do real useful work and would want to! e.g. if I create a very detailed playbook of how to make certain code improvements, ones that wouldn't be worth my time to do myself one-by-one, but if I had 200 interns and an automated way to verify that they did a good job, then sure!

The article says "manage a team of AI agents". Managing in this sense isn't like managing a human; it's like writing a shell-script to manage some bulk process.

Bingo. (no mod points today)

I wish I had mod points for this. My son-in-law works in this stuff and he's been frustrated about resistance to carbon-reduction efforts. The specific one he mentioned a while back I believe involved adding a (possibly calcium-containing) base to let a precipitate fall onto the sea bed sequestering the carbon. People were worried about sticking basic chemicals into the sea without realizing that reducing acidity itself was good in addition to carbon sequestration - that they're actually related.

I think there is for sports. Watch soccer on a 4k TV. The camera is usually pulled back far enough to see a lot of the field, so each individual player on a 4k screen (3840x2160) is about 150 pixels tall, and the number of their jersey is about 30 pixels tall. That's usually not enough for me to make out what's happening. I can make it out better live in person. An 8k screen I think would be enough to make it out. I'd sit closer to it than your 8' if I wanted to watch. (Likewise, at IMAX I like to sit about 5 rows from the front so the screen fills my peripheral vision).

I'm a senior developer and use LLM assistance multiple times an hour. >90% of the time I find something valuable in what it produced (even though rarely accept what it suggested directly, and I often write or rewrite every single line).

So what value does it have if I'm not accepting its code overall? Lots of value....
1. As a professional I produce code that (1) I can reason about why it's correct in all possible environments, (2) I'm confident that the way I've expressed it is the best it can be expressed in this situation. The LLM can spit out several different ways of expressing it, helping me assess the landscape of possible expressions, allowing me to refine my evaluation of what's best. (It doesn't yet help at all with reasoning about correctness).
2. About 10% of the time I accept some of the lines it suggested because they save some inescapable boilerplate. Or it spits out enough boilerplate to tell me hey, I need to invent an abstraction to avoid boilerplate here. I'd have gotten there myself too, just slower.
3. Sometimes I find myself learning new idioms or library functions from its suggestions.

I think management is right to be AI crazy. LLMs have increased the rate at which I solve business needs with high quality code, and I think my experience generalizes to other people who are willing to take it on and "hold it right". (Of course, there'll be vastly more people who use it to write low quality code faster, and it'll be up to management to separate the good from the bad just like it always has been.)

The risk is relatively high. Because a lot of lost phones end up in the seat back hinge area. So, you move a seat up for landing and now you have a lever practically designed for bending fragile phone cases in half. A lost phone just sitting on the floor is one level of risk. A lost phone potentially inside a levered lamp is another order of magnitude risk of fire.

You would be surprised. My wife lost her phone on a flight last year. It fell out of her pocket and into the seat crack. As required, we had the flight attendant help find it. It took a surprisingly long time to find. It turns out it wasn't in the seat at all, it had managed to slip out the bottom and the people behind us must have then accidentally kicked it another row back and it was kind of bounced/wedged against one of the seat legs on the outer wall side upright. Very tricky because we weren't looking in the right row even. It wasn't somewhere that was inaccessible, we just could not find it.

I guess the reason they care so much is because if it got into a hinge mechanism someone putting their seat back would definitely crack it open. The chances of a phone randomly igniting are nearly zero. The chances of a phone getting pried in half catching fire are very high.