Here's where the summary goes wrong:

Artificial Intelligence is in fact many kinds of technologies. People conflate LLMs with the whole thing because its the first kind of AI that an average person with no technical knowledge could use after a fashion.

But nobody is going to design a new rocket engine in ChatGPT. They're going to use some other kind of AI that work on problems on processes that the average person can't even conceive of -- like design optimization where there are potentially hundreds of parameters to tweak. Some of the underlying technology may have similarities -- like "neural nets" , which are just collections of mathematical matrices that encoded likelihoods underneath, not realistic models of biological neural systems. It shouldn't be surprising that a collection of matrices containing parameters describing weighted relations between features should have a wide variety of applications. That's just math; it's just sexier to call it "AI".

I wonder if they'll discover bulletin board systems (BBS) like we used to use before the internet was even a thing.

Seems to me there might be a proliferation of such systems appearing in Oz. I wonder if they could even "import" content from other mainstream social media platforms such as Facebook, YouTube etc like FidoNet used to do with usenet postings. Now *that* would be interesting.

Hey... come to think of it, let's just revive usenet and be done with it!

He's probably like one of those people who knows that Africa has been fucked over by other nations as long as there have been other nations to fuck them over. Everyone's had a turn abusing Africa.

Your first full paragraph is 100% opinion. Run along now.

They tried to do Jesus, but passengers kept calling security about a hippy boarding the plane.

AS I recall, someone tried using chemical SNAP generators with lasers and Neural Networks in the 1980's or 90's.
The system tried to shoot down the moon. Again. Happened before too, with a straight radar system (the Soviets tried? Might have been the US, I forget).

Pretty much. The lady that did the spreadsheet was shocked that it worked much better as a web application. She asked for PHP and SQL training. I helped her get the first basics, then since she wanted to change professions pointed her to professional training. I was concerned I'd show her bad habits, not being expert in it.

Investment is a tricky one.

I'd say that learning how to learn is probably the single-most valuable part of any degree, and anything that has any business calling itself a degree will make this a key aspect. And that, alone, makes a degree a good investment, as most people simply don't know how. They don't know where to look, how to look, how to tell what's useful, how to connect disparate research into something that could be used in a specific application, etc.

The actual specifics tend to be less important, as degree courses are well-behind the cutting edge and are necessarily grossly simplified because it's still really only crude foundational knowledge at this point. Students at undergraduate level simply don't know enough to know the truly interesting stuff.

And this is where it gets tricky. Because an undergraduate 4-year degree is aimed at producing thinkers. Those who want to do just the truly depressingly stupid stuff can get away with the 2 year courses. You do 4 years if you are actually serious about understanding. And, in all honesty, very few companies want entry-level who are competent at the craft, they want people who are fast and mindless. Nobody puts in four years of network theory or (Valhalla forbid) statistics for the purpose of being mindless. Not unless the stats destroyed their brain - which, to be honest, does happen.

Humanities does not make things easier. There would be a LOT of benefit in technical documentation to be written by folk who had some sort of command of the language they were using. Half the time, I'd accept stuff written by people who are merely passing acquaintances of the language. Vague awareness of there being a language would sometimes be an improvement. But that requires that people take a 2x4 to the usual cultural bias that you cannot be good at STEM and arts at the same time. (It's a particularly odd cultural bias, too, given how much Leonardo is held in high esteem and how neoclassical universities are either top or near-top in every country.)

So, yes, I'll agree a lot of degrees are useless for gaining employment and a lot of degrees for actually doing the work, but the overlap between these two is vague at times.

I too bought memory in April to avoid tariffs. I had to run a stupid python program to generate a dataset that required 96GB of RAM for a delayed project so I figured I might as well bite the bullet. DDR4 was still a good value at that point (it's a problem that can run overnight, performance wasn't too important).

But how are the tariffs limiting the manufacturing supply capacity of RAM factories in East Asia?

Do you have a mechanism to propose?

Do you think they're making enough to meet demand but then blaming tariffs to justify jacking up prices? All of them? It would be an interesting conspiracy but is there any evidence to support that theory?

> How much is this problem is down to AI and how much to beautiful tariffs?

What mechanism are you thinking of where tariffs could limit supply of VRAM from East Asia?

Simple price increases, sure, definitely, but this is described by manufacturers as a supply & demand problem.

Do you have a different angle we should consider?

The degree isn't about "getting a high-paid job", it's about knowing what the hell you're doing once you get a job. Although, fair enough, it's quite plausible that not many degrees would meet that standard either.

There is a possibility of a short-circuit causing an engine shutdown. Apparently, there is a known fault whereby a short can result in the FADEC "fail-safing" to engine shutdown, and this is one of the competing theories as the wiring apparently runs near a number of points in the aircraft with water (which is a really odd design choice).

Now, I'm not going to sit here and tell you that (a) the wiring actually runs there (the wiring block diagrams are easy to find, but block diagrams don't show actual wiring paths), (b) that there is anything to indicate that water could reach such wiring in a way that could cause a short, or (c) that it actually did so. I don't have that kind of information.

All I can tell you, at this point, is that aviation experts are saying that a short at such a location would cause an engine shutdown and that Boeing was aware of this risk.

I will leave it to the experts to debate why they're using electrical signalling (it's slower than fibre, heavier than fibre, can corrode, and can short) and whether the FADEC fail-safes are all that safe or just plain stupid. For a start, they get paid to shout at each other, and they actually know what specifics to shout at each other about.

But, if the claims are remotely accurate, then there were a number of well-known flaws in the design and I'm sure Boeing will just love to answer questions on why these weren't addressed. The problem being, of course, is that none of us know which of said claims are indeed remotely accurate, and that makes it easy for air crash investigators to go easy on manufacturers.

It's easy to have unique keys in your spreadsheet so that you can easily relate information on different sheets to one another. The problem is, actually doing the processing that a SQL server would do trivially is irritating, and then it will be processed slowly every time. Whatever Excel does or doesn't cache, it isn't enough. You can do big complicated things, but they work slowly, and maintaining it is irritating at best. When you do complicated things either your formulas get long, or you wind up having to write code, or in fact often it's both. At that point you're way better off IMO doing it in something else so that at least performance is good when you're done, and you never have to screw with editing a long formula.

That's exactly why it should be in a database and not a spreadsheet. Spreadsheets are best when you have a reasonably limited number of columns. It's also a horrible PITA to use them as a relational database (it's more or less possible, but you don't want to do it) so hiding pieces of that complexity in other sheets in order to limit the data the user interfaces with on the main sheet is just a lot of extra work you wouldn't have to do if you used another solution.

It doesn't really matter where it fails, if Excel can do it and Sheets can't then Google has to admit inferiority to Microsoft which is never a good look.