rhplus

Why are we even questioning this? They’re bytes loaded into GPU memory. Reboot the cluster and they’re back to their initial state.

> Anthropic treated a group of religious thinkers to dinner at a high-end tasting menu restaurant in San Francisco after a long day.

Well funded company organizes PR event to shape the narrative that its product is more magical than it really is. News at 11.

By 2001 the Internet - or specifically the web - had already bubbled and crashed. If anything, 2001 was the reset for the start of Web 2.0

Their contention seems mainly focused on the heavy resource use of AI tooling.

They run a service: they could impose limits on the number of submissions, builds, branches, scans, etc, and give additional usage credits to the large community projects they want to encourage.

What happens to all the precious metals that go up with these data centers? At least with a land based data center we have a vague hope of recycling the raw materials at some point in the future.

I think this article highlights more the importance of understanding system limits in the 1990s versus today. No-one would care to much today if the code review for this feature had “files.count()” or whatever in it, but in the mid 90s that would have been a huge performance red flag because a user would literally hear their hard drive clicking away and see the blinkenlights.

Kind of out there, but if you were running a network of agents that are autonomously looking for exploits, then perhaps those agents have decided that a good source of fresh ideas might be to periodically receive Schneier’s newsletter in an inbox they control.

> not always your first exposure

Great point. How many professional sports players credit their elementary aged PE classes to their success in sport (as opposed to say crediting a high school coach)?

Progressive, unbridled access and exposure is key.

> unenumerable amount of knowledge, tips and experience silently disappears

Not to be negative about experts here, but of all industries, isn’t airline maintenance one of the most documented and standard procedure focused of them all? I would hope that someone maintaining a 777 doesn’t have to remember certain tricks or tips outside of what the manuals say, and when mistakes are found, they’d be noted, investigated and republished to all maintenance crews worldwide.

I sense this is not winnable for all Wordle dictionary words. Is that provably the case?

Don’t forget operations and maintenance. You can have a box of vibe coded custom tools and services, but they’re all going to slowly rot as the underlying dependencies - network APIs, platform APIs, auth handshakes, reverse engineered file & DB schemas - change their behaviors and availability.

Sure, an LLM can fix it, but that assumes your original spec sufficiently described the user requirements and wasn’t just a transcript of the original session trying to figure out how how to interface with all those dependencies in the first place.

> Touching face, chest, groin, etc is forbidden.

It’s really hard to believe that an officer who’s wrestling someone hand-to-hand, possibly on the ground or against a wall, is going to restrain themselves from grabbing face or chest in the heat of the moment.