In an alternate universe, devs live in their own country.

They make their own rules and dictate how much they are paid. They maintain the entire world’s infrastructure.

They don’t go to work, since their entire country is the workplace and guess what? Cold beers are free(a thank you from the beer company guys for coming up with all their inventory management systems)

Pizza is free too.

There is no government (laws are passed depending on upvotes on devRant )

No racism, sexism or any other ism ending words . Devs just code.

Oh, and the state police, preferably known as keyboard warriors patrol the streets and offenders are punished by limited internet speeds. 😂. It is said some actually commit suicide because of this unbearable punishment.

Fuck yeah they have coffee farms. That’s the only thing they don’t accept as *gratitude from other nations because those sons of bitches might fuck that up too.

And everyone drives teslas 😂

Okay I have to get back to work now. That multi universe travel machine won’t buy itself.

So... did I mention I sometimes hate banks?

But I'll start at the beginning.

In the beginning, the big bang created the universe and evolution created humans, penguins, polar bea... oh well, fuck it, a couple million years fast forward...

Your trusted, local flightless bird walks into a bank to open an account. This, on its own, was a mistake, but opening an online bank account as a minor (which I was before I turned 18, because that was how things worked) was not that easy at the time.

So, yours truly of course signs a contract, binding me to follow the BSI Grundschutz (A basic security standard in Germany, it's not a law, but part of some contracts. It contains basic security advice like "don't run unknown software, install antivirus/firewall, use strong passwords", so it's just a basic prototype for a security policy).

The copy provided with my contract states a minimum password length of 8 (somewhat reasonable if you don't limit yourself to alphanumeric, include the entire UTF 8 standard and so on).

The bank's online banking password length is limited to 5 characters. So... fuck the contract, huh?

Calling support, they claimed that it is a "technical neccessity" (I never state my job when calling a support line. The more skilled people on the other hand notice it sooner or later, the others - why bother telling them) and that it is "stored encrypted". Why they use a nonstandard way of storing and encrypting it and making it that easy to brute-force it... no idea.

However, after three login attempts, the account is blocked, so a brute force attack turns into a DOS attack.

And since the only way to unblock it is to physically appear in a branch, you just would need to hit a couple thousand accounts in a neighbourhood (not a lot if you use bots and know a thing or two about the syntax of IBAN numbers) and fill up all the branches with lots of potential hostages for your planned heist or terrorist attack. Quite useful.

So, after getting nowhere with the support - After suggesting to change my username to something cryptic and insisting that their homegrown, 2FA would prevent attacks. Unless someone would login (which worked without 2FA because the 2FA only is used when moving money), report the card missing, request a new one to a different address and log in with that. Which, you know, is quite likely to happen and be blamed on the customer.

So... I went to cancel my account there - seeing as I could not fulfill my contract as a customer. I've signed to use a minimum password length of 8. I can only use a password length of 5.

Contract void. Sometimes, I love dealing with idiots.

And these people are in charge of billions of money, stock and assets. I think I'll move to... idk, Antarctica?

One of biggest epiphanies came through this fundamental critique in SICP of the assignment operator. Through years of imperative programming it seems so innocent, doesn't it? But that you lose referential transparency, run into the alias problem and fundamental difficulty to determine object equality (or of their instances) - that was kind of eye opening considering all the pain I had already experienced with state in concurrency.
(It led me so far to think it's an ontological issue, that even in the discrete computing universe we have not come so much further than Zenon's paradoxa on change.)

Being able to summon CTRL+Z's and/or save timestamped Universe state snapshots.

The distance between two nearest hydrogen atoms inside recursion function is the key to understand the universe.

But which hydrogen atoms we need to pick from the whole universe to see it ?

How to identify them if after each iteration the order of operations changes based on results and we only see the previous state as an argument of function.