There’s no evidence of that here, but I’m fine with right-wing conspiracy crazies freaking out over the possibility.

Fair point. But our cars? Nah.

Yeah, good luck with that. No one’s gonna buy our rice or shitty, gas-guzzling cars over there because of this trade war shit, so this is basically just Trump announcing a 15% tax on consumers who want to buy stuff from Japan.

Nah, he was old and sick, so it’s probably natural causes, but it certainly won’t help the conspiracy theorists on the right who’ve been flailing around over Epstein.

Translation: Military bases in New Jersey, Indiana, to be turned into concentration camps.

Yeah, but the price of eggs…

Dude, read the room. Yeah, your road probably needs to be repaired, but not with that money.

That’s how it begins. Gradually, you’ll see things you’re used to always having in stock disappear, while other things become steadily less affordable. It’s nothing that happens all at once, just a slow boiling of the frog until supermarket shelves are a wasteland.

Banning open source would basically destroy the entire Internet in the United States. No tech bro is going to want that.

We’re in a war of attrition with his cult. Every time something like this happens, a few of them reach the point where they can’t stand the cognitive dissonance anymore and start coming out of the fugue he’s kept them in.

I know a lot of them will shove everything they thought about Trump and the Epstein files down the memory hole. But a few won’t. Hopefully enough.

I hate the fact that we just accept this unconstitutional bullshit now without even calling it out as unconstitutional.

Congress is the only governmental body empowered to levy tariffs. Every single one of Trump’s tariffs-by-fiat has been a direct and blatant violation of the constitution.

So now departments of the government that were created by Acts of Congress are just… null and void if King Trump says so?

That’s fair. I guess what I hate is what the term represents, rather than the term itself.

I actively hate the term “vibe coding.” The fact is, while using an LLM for certain tasks is helpful, trying to build out an entire, production-ready application just by prompts is a huge waste of time and is guaranteed to produce garbage code.

At some point, people like your coworker are going to have to look at the code and work on it, and if they don’t know what they’re doing, they’ll fail.

I commend them for giving it a shot, but I also commend them for recognizing it wasn’t working.

That’s still not actually knowing anything. It’s just temporarily adding more context to its model.

And it’s always very temporary. I have a yarn project I’m working on right now, and I used Copilot in VS Code in agent mode to scaffold it as an experiment. One of the refinements I included in the prompt file to build it is reminders throughout for things it wouldn’t need reminding of if it actually “knew” the repo.

• I had to constantly remind it that it’s a yarn project, otherwise it would inevitably start trying to use NPM as it progressed through the prompt.
• For some reason, when it’s in agent mode and it makes a mistake, it wants to delete files it has fucked up, which always requires human intervention, so I peppered the prompt with reminders not to do that, but to blank the file out and start over in it.
• The frontend of the project uses TailwindCSS. It could not remember not to keep trying to downgrade its configuration to an earlier version instead of using the current one, so I wrote the entire configuration for it by hand and inserted it into the prompt file. If I let it try to build the configuration itself, it would inevitably fuck it up and then say something completely false, like, “The version of TailwindCSS we’re using is still in beta, let me try downgrading to the previous version.”

I’m not saying it wasn’t helpful. It probably cut 20% off the time it would have taken me to scaffold out the app myself, which is significant. But it certainly couldn’t keep track of the context provided by the repo, even though it was creating that context itself.

Working with Copilot is like working with a very talented and fast junior developer whose methamphetamine addiction has been getting the better of it lately, and who has early onset dementia or a brain injury that destroyed their short-term memory.

Like I said, I do find it useful at times. But not only shouldn’t it replace coders, it fundamentally can’t. At least, not without a fundamental rearchitecturing of how they work.

The reason it goes down a “really bad path” is that it’s basically glorified autocomplete. It doesn’t know anything.

On top of that, spoken and written language are very imprecise, and there’s no way for an LLM to derive what you really wanted from context clues such as your tone of voice.

Take the phrase “fruit flies like a banana.” Am I saying that a piece of fruit might fly in a manner akin to how another piece of fruit, a banana, flies if thrown? Or am I saying that the insect called the fruit fly might like to consume a banana?

It’s a humorous line, but my point is serious: We unintentionally speak in ambiguous ways like that all the time. And while we’ve got brains that can interpret unspoken signals to parse intended meaning from a word or phrase, LLMs don’t.

Experienced software developer, here. “AI” is useful to me in some contexts. Specifically when I want to scaffold out a completely new application (so I’m not worried about clobbering existing code) and I don’t want to do it by hand, it saves me time.

And… that’s about it. It sucks at code review, and will break shit in your repo if you let it.

“Scientists”

You keep using that word. I do not think it means what you think it means.