Some who already want RTO may use this as an excuse, but I would think it would actually reduce RTO pressure overall, as it confirms less short-term productivity, which is what companies actually care about.

You have to be willing to accept "close-ish and good enough" to what you'd write yourself. I would say that most of the time I spend with Claude is to get from its initial try to "close-ish and good enough". If I was working on tiny changes of just a few lines, it would definitely be faster just to write them myself. It's the hundreds of lines of boilerplate, logging, error handling, etc. that makes the trade-off close to worth it.

Killing the corrupt guards, often one at a guard tower in the Plains of Karanas west of town, and turning in their bracelets to a non-corrupt guard at the bridge to South Karanas, was great XP for quite a few levels in the midgame. And it is possible to repair the corrupt guard XP (slowly) with low-level quests.

> ... The price elasticity of import demand, ε, was set at 4.

> ... The elasticity of import prices with respect to tariffs, φ, is 0.25. ...

Lots of places (including a former employer) have done tons of work to upgrade internal infrastructure to support HTTP/2 just so they could use gRPC. The performance difference from JSON-over-HTTP APIs was meaningful for us.

I realize there are other solutions but this is a common one.

As far as what Google is doing in the bug bounty, that's a good question -- we don't know. The author is proposing two new values, for the domain and user, that wouldn't change in the cases that sub changes now, but would change in this case.

In my experience, that access control is necessary for several reasons (mistakes due to inexperience, cowboys, compliance requirements, client security questions, etc.) around 50-100 developers.

This isn't just "not zero trust", it's access to everything inside the cluster (and maybe the cluster components themselves) or access to nothing -- there is no way to grant partial access to what's running in the cluster.

Note that in Tim's response at the bottom of the article, he says clearly he believes the board that the details can't be shared and that they are serious.

They go on to say that the solution is sandboxing, but still, this feels like burying the lede.

I've spent a fair amount of time listening to free audiobooks (https://archive.org/details/librivoxaudio) including many that are out of copyright like these, as opposed to modern but in the public domain.

After listening to a few minutes of "Frankenstein" on his site, I would say that these OpenAI generated voices sound better than almost all of the human-read ones on Librevox, both in audio and performance quality -- these are voices that are designed to sound good, and they succeed at that.

Worth . . . noting . . . that every file with license info says MIT; none say anything else. So the "unless otherwise noted" is purely future-proofing.