I see it kind of like baking/cooking. Do you bake your bread from scratch? Do you grow your own wheat and grist your own flour?

I think over reliance on it or not even trying to understand what is happening is a big problem to be sure, but it's certainly not a new problem.

Not just Trump, Republicans as a whole. They are not fiscally conservative at all, and their culture wars and religious crusades are going to bankrupt the nation.

They'll sell you up a rope to corporate donors asking for deregulation. And we've seen exactly what happens when there is money to be made at the expense of other people's lives: spoiler alert, people like money more than they care about other people's health.

If people could imagine it being used against them, maybe they might understand. Like labeling the Republican party a terrorist organization because they sponsored Jan 6 insurrectionists.

What does this even mean?

I'd argue that having the source to build the thing is more important than the artifacts. Release artifacts are more of a convenience. If the thing doesn't build from the source given, what use is it?

If you can't write to the filesystem, almost everything you do in an embedded system will fail. So you can't undo a partial write. Your logging will probably fail too.

A relatively big database (a tier 2/3 database) that I was using handled this in a really bad manner: it'd just segfault. Depending on when this happened you could get data corruption and never be able to open the DB even in read-only mode.

It's one of the core principles of a database! And it didn't even do that correctly.

No social media? People will still find ways to socialize. It might not be as easy, but they will do it. Maybe you'll even see a resurgence in social clubs.

Do you read over what the AI spits out? Do you read over what you write?

It takes time to do either, and both are the things that I think are actually useful.

I think enforcing black box testing is the best way to get useful tests out of both humans and robots. They must not know the internals, or it will lead them to do bad things.

Just because someone moved on from your broke ass product doesn't mean the bug was fixed. I can't count how many times I'll find an old bug still there years later closed with 5+ duplicate issues all linked back to the same closed github issue that was closed as stale.

It's just bullshit. Having a lower count on your issue tracker doesn't make the actual bugs disappear folks

LLMs don't fix that though. I see some truly awful code come out of them. And no, it's not just better context or use more skillz.md.