You test your backup by recreating your system, either in a local environment or in some cheap simulated one.

It’s even better if you write a manual with the steps you needed. And try to follow (and update it) when you do it again.

I figure the most bang for my buck right now is to set up off-site backups to a cloud provider.

If you don’t have the budget for on-premises backup, you almost certainly can’t afford to restore the cloud backup if anything goes wrong.

Then I started reading about backing up databases

Go read the instructions for your database in particular. They are completely different from each other. Ignore generic instructions.

now I’m configuring a docker-db-backup container

What is perfectly fine. But I’d first look how this interferes with the budget you talked about earlier and if it wouldn’t be better to keep things simpler and put the money on data replication.

Either way, if your budget is low, I’d focus a lot on making sure you have the data when you need to restore, and less on streamlining the restore procedure. (That seems to be the direction you are going, so yeah, I’d say it’s good.) Just make sure to test the restore procedure once in a while.

Just like functional programing is about making state explicit, not making it go away.

Overall, both arms are wrong… so they cancel out or something like that.

And it still doesn’t work. Just “mostly works”.

Good luck, the instances can’t just be started in any random order and at their current version their dependency graph is cyclical.

If you think it’s jarring to mix names from different languages with English keywords… well, I have bad news for you.

The language is entirely in English. Only the comments and values are in Portuguese.

You think that about math not being localized too?

That “most likely no one is bothered” part is correct, though.

If they are Perl regexes, like all regexes are supposed to be, you can have non-semantic whitespace and comments.

But if you are using some system that enforces something different, you are out of luck.

That’s why we don’t call them “programming language” even though they are the same kind of thing.

At some point you’ll need to know the basic syntax of some programing language.

int main() {
    useless:
    int x = 10;
    if (1) {
        goto useless;
    }
}

With plans to impose much higher tariffs on the __future__.

The one thing about NT was that it didn’t have it’s own semantics, but it could emulate any system you wanted. It’s the unofficial successor of an OS that was based on creating VMs where you could run any other OS you want.

Then Microsoft decided to create their own system in it, and only really finished writing that one.

It’s the way.

It certainly beats Teams, Slack, or Discord. For a start, you have control over the messages and can actually search on them.

== has essentially no use unless you remember some completely arbitrary rules

If you make sure the types match, like by explicitly converting things on the same line on that example, then you can use it just like if it was ===.

In fact, there are people that defend that if your code behaves differently when you switch those two operators, your code is wrong. (Personally, I defend that JS it a pile of dogshit, and you should avoid going to dig there.)

Yes. Yes, it is.

Good thing I can’t sign my rights away that easily in my country.

I think I can even compare it with Postgres and tell people Postgres is faster! Well, not in every single case, but Oracle is beaten by almost every DB in almost every case.

Yeah, fixed something like this yesterday.

Turns out the Oracle database can’t count lines. But that’ not really news.