I feel like it would be more appropriate is regular running wore button and running as administrator was a dude casually strolling down the pavement in sweat pants.

:(){:|: &};:
:(){:|: &};:

The intention was to provide a longer version for the first step of the ladder.

function() {}

Screenshot from https://www.atlasobscura.com/places/fucking-austria because they’ve changed the spelling to “Fugging” after the village got famous.

I don’t know if you’re sarcastic or don’t know, and either way it doesn’t matter. Here’s the README from the first commit in git:

"git" can mean anything, depending on your mood.
 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronounciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room. 
 - "goddamn idiotic truckload of sh*t": when it breaks

To be honest, I’ve been using GIMP for more than 10 years before I learned of the slur.

Similarly, git.

My company dabbles in AI. A hardly abridged conversation with a bot I’ve read recently:

Hallo, Ich bin ein Bot. Wie kann ich Ihnen helfen?
(Hi, I’m a bot. How can I help you?)

Speak English, please.

Gerne antworte ich in Englisch. Wie kann ich Ihnen helfen?
(I’m happy to speak English. How may I help you?)

Caller disconnected

Yep, AI definitely is the future.

If you’re iterating over a whole array and need the index, like in ll.15f., you can instead write

particles.forEach((particle, i) => {
  // loop body
})

There may be a performance hit (I haven’t tested it) because you’re invoking a function on each iteration. And it’s mostly a stylistic choice.

Line 10: indentation

Is “syntax” a bad word now? Don’t dumb things down for students, elevate the students!

try a new distro if you’re having that many problems with Mint

I’ve had problems across all the “beginner” distros: Ubuntu, Mint, Manjaro. The biggest reason why I tried so many is because two out of three always had issues out of the box. When the time came when the LTS died, it was a different set with problems.

On two different laptops.

If something breaks when I update the kernel and that same thing works again if I downgrade the kernel, what explanation should I seek other than that the kernel broke something?

Notice I’m on Linux Mint, so I’m not using the original kernel but a modified version.

Because whenever I’ve upgraded any Linux OS in the last 10 years, something broke. Always. That’s why I’m riding this LTS until it dies.

I’m using the 21.3 LTS release. That may be why I have more kernel options.

Since in my experience something always breaks when upgrading any Linux OS, I’ve come to try to avoid that.

Luckily I learned programming when I was already using the NEO layout. I couldn’t imagine typing parentheses and the like in German…

The first step in any software project is not doing it. Have you checked if the product you want to build isn’t already out there?

Imagine thinking about what you’re going to code beforehand. What a world we live in!

Let’s be real here. The problem isn’t that it’s “too complicated” to list the fees. What’s complicated about listing a few numbers? The problem is that they don’t want to list a myriad of fees.

The fact that “tell your customers what you will charge them” is a rule that had to be instantiated in the Biden legislation is in itself a joke.

Single responsibility. I deplore my backend developers who think that just because you’re mauling a single (Java) stream for an extended operation, it’s ok to write a single wall-of-text, 5 lines long, 160 characters wide. Use fucking line breaks, for fuck’s sake!