Yeah but radio ads are generic and not 2 way conversations. They are not an asking what you are saying and twisting it towards explaining why you need product X.

It will be as reliable as asking a used car salesman for advice. Somehow it's gonna be advice about how a car would for me

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.

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 far from indisputable. Indeed, it's hotly disputed within the aviation industry. That does NOT mean that it was a short-circuit (although that is a theory that is under investigation), it merely means that "indisputable" is not the correct term to use here. You can argue probabilities or reasonableness, but you CANNOT argue "indisputable" when specialists in the field in question say that it is, in fact, disputed.

If you were to argue that the most probable cause was manual, then I think I could accept that. If you were to argue that Occam's Razor required that this be considered H0 and therefore a theory that must be falsified before others are considered, I'd not be quite so comfortable but would accept that you've got to have some sort of rigorous methodology and that's probably the sensible one.

But "indisputable"? No, we are not at that stage yet. We might reach that stage, but we're not there yet.

I think this view gives the crypto bros too much credit. They might now be thinking about taking advantage of the opportunity to wrestle the system away from the Wall Street bros, but there was no such plan.

To intercept them you still have to identify them, which you can't do until after they perform the sabotage. Given that, what's the benefit in sinking them rather than seizing them? Sinking them gains you nothing, seizing them gains you the sabotage vessel. It probably won't be worth much, but more than nothing. I guess sinking them saves the cost of imprisoning the crew, but I'd rather imprison them for a few years than murder them.

Very much unlike an intern (the doing-over part).

You ignored his core point, which is that "rocks don't think" is useless for extrapolating unless you can define some procedure or model for evaluating whether X can think, a procedure that you can apply both to a rock and to a human and get the expected answers, and then apply also to ChatGPT.

Heh. It says a lot about the pace of AI research and discussion that a paper from last year is "old".

This is a common thread I notice in AI criticism, at least the criticism of the "AI isn't really thinking" or "AI can't really do much" sorts... it all references the state of the art from a year or two ago. In most fields that's entirely reasonable. I can read and reference physics or math or biology or computer science papers from last year and be pretty confident that I'm reading the current thinking. If I'm going to depend on it I should probably double-check, but that's just due diligence, I don't actually expect it to have been superseded. But in the AI field, right now, a year old is old. Three years old is ancient history, of historical interest only.

Even the criticism I see that doesn't make the mistake of looking at last year's state of the (public) art tends to make another mistake, which is to assume that you can predict what AI will be able to do a few years from now by looking at what it does now. Actually, most such criticism pretty much ignores the possibility that what AI will do in a few years will even be different from what it can do now. People seem to implicitly assume that the incredibly-rapid rate of change we've seen over the last five years will suddenly stop, right now.

For example, I recently attended the industry advisory board meeting for my local university's computer science department. The professors there, trying desperately to figure out what to teach CS students today, put together a very well thought-out plan for how to use AI as a teaching tool for freshmen, gradually ramping up to using it as a coding assistant/partner for seniors. The plan was detailed and showed great insight and a tremendous amount of thought.

I pointed out that however great a piece of work it was, it was based on the tools that exist today. If it had been presented as recently as 12 months ago, much of it wouldn't have made sense because agentic coding assistants didn't really exist in the same form and with the same capabilities as they do now. What are the odds that the tools won't change as much in the next 12 months as they have in the last 12 months? Much less the next four years, during the course of study of a newly-entering freshman.

The professors who did this work are smart, thoughtful people, of course, and they immediately agreed with my point and said that they had considered it while doing their work... but had done what they had anyway because prediction is futile and they couldn't do any better than making a plan for today, based on the tools of today, fully expecting to revise their plan or even throw it out.

What they didn't say, and I think were shying away from even thinking about, is that their whole course of study could soon become irrelevant. Or it might not. No one knows.

You do realize that what you're describing is all of about ten lines of Javascript with the right libraries (audioTrackList property, subtitle library, currentTime property), right?

Great opportunity for open source web services. :-)