I highly doubt it, most frameworks do indeed automatically prevent it these days. Still funny though.

No doubt. git rebase is like a very sharp knife. In the right hands, it can accomplish great things, but in the wrong hands, it can also spell disaster.

As someone who HAS used it a fair amount, I generally don’t even recommend it to people unless they’re already VERY comfortable with the rest of git and ideally have some sense of how it works internally.

Here’s another one, catch!

IDK, virus scanners and malware detectors could do these things before AI.

You could search for stuff like directly accessing the ~.ssh directory, or any invocations of wget or curl to download external scripts and run them through an interpreter and flag those for closer inspection.

If you want to get fancier, automate installing packages in an isolated environment (like a container or VM) and keep track of every file system access and network request they make.

Sure, eventually they’ll figure out ways to obfuscate those things, too, but it could at least prevent people from doing things in such blatantly obvious ways.

“Abandon all hope, ye who enter here.”

As someone who has experienced burnout before: that’s exactly what it looks like.

GitLens?

GitHub Desktop is literally “Baby’s first git GUI”.

You mean these? Does it use them internally, because I haven’t really seen them in any Svelte code.

If so, what does it matter what the compiler does in order to make your code work, so long as it’s legal? It’s perfectly valid JS, that’s all that counts.

I wouldn’t say Svelte is weird as much as it’s different. That’s the whole point after all. Instead of adding a bunch of library bloat and keeping an entire copy of the DOM to constantly compare to and derive changes from, it compiles your components down to native JS that manipulates the DOM directly, like you would by hand. Except of course the compiler uses different ways to achieve that than you would, but that’s because it doesn’t have to care about readability, as long as it creates valid and efficient code.

Both are weird compared to Svelte.

Well yes, internally that’s what it does, but from a user perspective it just looks like being handed the package, you never see any of the failed attempts (unless delivery fails completely because the company went out of business). It’s sorta more like having a butler who orders it for you and deals with any potential BS that might happen, and then just hands you the package when it finally arrives in one piece.

It really doesn’t matter. Literally a Raspberry Pi will do for a beginner.

And jc, apparently: https://programming.dev/post/7063427

require 'castle'

begin
  Castle.attack
rescue Princess
  puts "Done"
end

from Castle import Princess

Done

Yes, but mostly because the general population likely isn’t super familiar with Bittorrent and PirateBay.

A better, yet similarly correct explanation would be to say GitHub is to Git what GMail is to email.

This also doesn’t confuse protocol and content, and it doesn’t require knowledge of piracy.

How do you calculate those numbers though?

It’s not like your colleagues will be keeping track of how much time they’ve wasted writing ineffective code. If anything, they’ll try to hide that by arbitrarily inflating sprint points etc.

I’ve worked in environments like that and the issue almost always isn’t that people wouldn’t LIKE it if there were tests, it’s that they

1. Don’t want to have to learn something new in order to do the same job they’re already comfortable with
2. Are worried that if they convince management to let them invest X amount of time into doing something that will improve productivity, they’ll be expected to be more productive in the future

And of course, all of this for no extra money. Unless you work at a place where management prioritzes developer happiness over how many sprint points the team can knock out every week (and those are rare), the sad truth is that it’ll likely be about as popular as leftover food growing mold in the community fridge.