no it’s the joke. In o-notation you always use the highest approximation, so o(n!²) does not exist, it’s only o(n!)

Otherwise there would never be o(1) or o(n), because o(1) would imply that the algorithm only has a single line of instructions, same for o(n)

I just googled “BASF T-Shirt” and immediately found the one he is wearing in this video (and he wear it in a couple of other videos recently)

Just using fluentd to push the files into an ElasticSearch DB and using Kibana as frontend is one day of work for a kubernetes admin and it works good enough (and way better than grepping logfiles from every of the 3000 pods running in a big cluster)

And if something breaks they put the burden on you for not creating backups. Always keep it in writing that you are supposed to work on something else, otherwise you will get the problem down the line

I updated my sources.list to something non-existing at some point and run sudo apt update && sudo apt dist-upgrade -y && sudo apt autoremove once and it also basically uninstalled everything. But that didn’t even matter, I popped in a recovery disk and could reinstall everything. Pretty great to be able to do all that with Linux, fuck everything up in an instant but after a few hours everything is back again

yeah thats why I said it only has the chance, not that it leads to good code

The only thing that has the chance to prevent unmaintainable garbage code is a plethora of linting rules.