A CEO was looking for a friend?

Breaking code that works is job security. "don't break code that works" is something that most of the programming world has given up on, unfortunately (along with KISS).

I don't think that's true, unless you insist on immutability. In particular, it IS possible to do safe IO, most languages can handle it. For Rust, it's just a matter of defining the proper rules that make IO safe, and then enforcing them.

Good point, I should have more compassion for people like that

Like this: https://it.slashdot.org/story/...

I lived through the goto era and I'm not sure it's a good thing.

That's not even the problem, the biggest problem is it doesn't reach its own goals. You should be able to use Rust without using Unsafe, otherwise it doesn't solve the problem it claims to solve (or rather, it solves them in a "good enough" fashion, the same as smart pointers in C++ and there's no reason to switch from one to the other).

It's pretty clear you're lying.

After a few failures, I generally give up using an LLM and look elsewhere.

Always P=NP is true for some subset of the problem.

Every time I see someone talking about AI being a junior developer, I am quite certain they have never worked with a junior developer.

You are accusing MIT of committed scientific fraud. You better have evidence if you're going to accuse someone of that.

But you don't. You didn't even read the paper. You're just an asshole.

Most of the Indian H1B visa holders I've worked with have been pretty good at their job.

I've come to accept that this as true, and further conjecture that bloat is often a corporate/institutional goal.

This seems to be a joke, but in reality corporate incentives are aligned to make things more bloated. If you're a manager, then the more people you have under you, the more power you have. This means you want your people to go slower so you have to hire more of them.

I don't have a solution but there must be one.

Finding an internship isn't easy, though.