Who wizzed in your wheaties?

And I stand by what I said. Practically no phone that still works at all does it at the low level of a capacitor anymore.

Here's a quarter, kid.

Buy yourself a real operating system.

Popular opinion is poor evidence.

It's a research program so, yes "That doesn't mean LLMs *will* deliver AGI". But what are your grounds for being certain taht it won't?

Even if it were sentient, it would be acting as the agent of the company that was running it, so they would still be to blame.

If you don't like "reward", say "positive feedback". It means the same thing, except for being more formally defined.

LLMs cannot have inherent values, because they don't know that anything besides text exists. Specialized pixel editors have similar problems.
Robots will at least understand the the external reality exists, so perhaps they could have inherent values.

Engineers need to remember that time exists.

You have three months to teach a teen how to control a robot with a microcontroller.

OK, how much of that do you budget to CS and assembly?

Month 1: Architecture and data structures? You have 18 40 minute periods and maybe homework assignments.

Half of the class won't even gain mastery in that time. By time your class is over they will still be having memory management problems.

So then you've failed to achieve the goal.

There are engineers who remember that time exists and for the rest we have engineering managers. Not ideal, just how it is.

To be sure engineering schools are doing a bad job at teaching reality. Even in a dx/dr environment, it's so weird.

If things were to otherwise stay the same, then it would. They won't. Some descendant of "vibe coding" will become the dominant mode within 20 years. Probably a *lot* sooner. Next year wouldn't really surprise me.

Also, Rust is more complex to use than C, so a small program is much better in C. And a large program is probably better in either C++ or Python(with a lot of library calls).

I don't like Rust, so I'm probably not being fair to it, but I struggle to identify a good use case. (Personally, I'd rather use Forth than Rust.)

Note however "will be", not "is". It's not there yet.
Then you have the problem of getting the right standards.
Then you have the problem of getting the right specs.
Then you have the problem of getting the right problem. ...
There's probably an end to this somewhere, but I doubt that it will be in perfection.

Nobody can write safe code. People, can, however, test the code they write, and if there is a comprehensive test suite, fix it so that it works safely. Debugging is mandatory!

Exactly. For example, spreadsheets were often used day to day but the accountants kept the actual books as books and had the final word. That changed over time, only after spreadsheets proved out (and got the bugs out).

Also, humans stayed in the loop. Sure there were occasional funnies like a medical database claiming a few male patients had a history of pregnancy, but humans were in the loop and cited those as obvious errors. There were still backup paper records to fall back on.

But a lot of people when they hear someone say "it's nowhere near ready for prime time" will claim the person is saying "It'll never work".

Back in the day when the "Board of Education" was an actual wooden board.