Mostly yes, but they’re in general oversimplified (for obvious reasons)

But it’s more about offensive cyber security than necessarily the Linux part. The Linux part is just file system navigation and not much more, the rest is the “hacking” part, and that’s what I’m talking about

Disclaimer: I did not complete it, but I got pretty far, and I worked in the cyber security area.

I would however say it’s not a good place if you want to learn as that’s not really the game’s focus. There are better resources out there like overthewire and linuxjourney for that

Seems like a potential circular reference though, judging from how popular Kurzgesagt videos are.

It depends heavily on region. I personally don’t think I ever had issues with parsers. I used the awesome CV template as a base. It’s fairly simple while still not being completely boring. You can find it on GitHub or overleaf iirc (it’s been a while).

Done it and highly recommend it

It’s my belief that it’s rare for evolution to screw up.

That’s not how it works, I’m pretty sure… Mutations will have random effects and the species evolves based on characteristics being selected for based on better survivability, reproductive effectiveness, etc.

I would do everything I could to find an alternative solution and talk them down from it.

I’ve read your other messages and it seems that you’re thoroughly convinced that this wasn’t the case here. I suggest that you get a bit more context about this whole situation, as it has been a long path of trying multiple treatments and approaches, without any success. So it’s not even remotely close to what you suggest here. No Futurama suicide chambers here.

Do people know you’re circumcised based on your skin colour? Seems like a facetious comparison

Wait, you’re not AI too?

Shared branches should always only move forward. Most Git-* systems support stuff like protected branches.

I personally like tidying up your own feature branch with rebasing and then merging it into main (preferably using only FF merges). However this is not scalable for some larger projects, and for example monorepos also make this hard to accomplish. In those cases the solution ends up being squash+merge.

The extra information about the squashed commits is usually persisted to these systems (GitHub PRs, GitLab MRs, etc) so you don’t really lose much, I guess. Although I do prefer keeping it all in plain git.

Nice reference

Hasn’t been the case anymore for quite some time, even though I think it has quite generous sudo rules. But yes, it’s not meant to be your main OS but instead more like a toolbox you use in liveboot/VM/etc.