... throughout the developed world. Especially for college grads. Same thing here in Germany too. The rate of unemployed academics has surpassed that of trades people, just like in the US. It's AI. Mostly.

... he sure is effing serious about getting us back into space. Good stuff, like it!

We get it. You don't like Beyonce. Neither do I, but I'm not making a scene over that fact.

... they're about selection. Mix those two things up and you won't get very far in solving this.

So by your definition, if there is a class of the best students that ever existed, a certain percentage should get an "F" to meet a quota?

It's this sort of South-Korean / Japanese style non-sense that has people work themselves to death or young people kill themselves.

If grade inflation is hurting the Havard brand, that's entirely on them and only happens if you make education a business as the US Ivy league does. Find objective criteria, document and publish them and rate the students by them. Problem solved. If more students get "A"s, then that's because the students and/or your teaching has gotten better.

This whole debate reveals what grades are really about. Not about education, but selection.

... point:

But YOU WILL USE AI for coding is here for non mission critical applications.

Nope. For generic stuff I would, as of now, trust the AI to do mission critical stuff better than any human as well. Point in case: Just yesterday the newest Codex fixed an oversight of mine while doing another task and _explained_ to me that he/she/it was fixing an oversight in order to properly do that other thing I asked for. This was a non-trivial detail concerning state management and recovery in a non-trivial SPA. Something a human would've needed a day or two for fixed in 3 minutes. That wasn't AI just coding, that was AI doing an architecture decision on it's own(!!) to fix the oversight. That's how far we've come with AI as of yesterday.

The biggest part of my job is for me to keep track of what we actually get done and document it after reviewing the code. And, yes, I have never had colleagues this competent either. I've mutated to a primary senior architect with a expert team of 20 within less than a year. If I were to still code myseld, I'd be the bottleneck. And a serious one. So, yeah, basically your assessment is spot on with my AI experience so far.

Nuclear reactors use most surface water, not ground water.

Datacentres are no pickier. You can even cool a datacentre with saltwater, you just need a heat exchanger.

Also, closed loop does not evaporate. The loop is not closed if stuff escapes from it.

You're arguing with the actual terminology used in the nuclear industry. "Closed loop" or "closed cycle" designs have the water pumped in a cycle through cooling towers. The towers lose water to evaporation, taking heat with them, but the rest of the water is returned to be reheated again. "Open loop" or "open cycle" designs have no cooling towers. The water is heated and just discharged hot. They consume much more water (over an order of magnitude more), but most of that is returned. Closed loop are more common, but you see open loop in some older designs, and in seawater-cooled reactors.

"How often do you think I print?"

Seemingly not very.

I've printed many hundreds of kg on my P1S, thanks.

I do not consider having to write data out to a card and transport it back and forth between the printer and the computer to be the pinnacle of convenience. That's something that would be considered embarrassingly inconvenient for a 1980s printer, let alone a modern net-connected device. And it's designed to be inconvenient for non-cloud prints for a reason.

Around 1990, I worked for a couple months on an embedded device that had an 80186 and a megabyte of RAM. At one point, I had access to a huge pile of 1MB SIMMs and took a stack home for the evening and using memory boards that allowed you to stack up to 8 of them into one SIMM slot in your computer to figure out just how little RAM Windows NT 3.5 really needed to boot. It booted successfully with 12MB of RAM. It really wasn't usable, but it did boot up. Nowadays, Windows is probably only marginally usable with 12GB of RAM.

... that's terrible. Aren't the team rioting already?

- You should've heard the noise when we called that cassette player "Walkman".

Discussion on the Sony Playstation 1 team, paraphrased.

Whoops. That's a bottom-rung typo if I ever saw one.

I'm pretty sure wether you're in ketasis (body produces it's on bloodsugar) or overbooked on sugar (which many often are) is a key factor in wether you're a prime target for mosqitoes. That would also totally make sense for them from a nutrition standpoint. If you're a mosqito magnet, try losing some wait and go into ketasis, perhaps with interval fasting. At least when they're out and about. That's likely do reduce or solve the problem.

Also, anything sounds big when you put it in gallons. Doesn't sound so big when you mention that's 92 acre feet, the amount used by less than 20 acres / 8 hectares of alfalfa per year. Or when you mention that a typical *closed loop* 1GW nuclear reactor uses 6-20 billion gallons of cooling water per year (once-through uses 200-500 billion gallons, though most of that is returned, whereas closed loop evaporates it)

I don't think it has anything to do with that. As soon as I saw the headline, my mind went "cohort study". And sure enough, yeah, it's a cohort study. Remember that big thing about how wine improves your health, and then it turned out to just be that people who drink wine tend to be wealthier and thus have better health outcomes? And also, the "sick quitter" effect, where people who are in worse health would tend to stop drinking, so you ended up with extra sick people in the non-wine group? Same sort of thing. This study says they're controlling for a wide range of factors, but I'd put money on it just being the same sort of spurious correlations.