Some declarations terminate on the name, other declarations go one requiring more tokens. In C, the only thing that differentiates them is the type.
Parenthesis in particular are completely ambiguous. But asterisks and square brackets also create problems.
Good, now invent a keyword for variables you don’t want to declare the type. And now that you have a mix of keywords and identifiers on the same place, you can never update your language again.
Also, make the function declarations not use a keyword too, so you get the full C-style madness of code that changes meaning depending on what libraries you import.
Even older variants required both a let to declare the variable and a dim to set its size.
I remember a REDIM command, but I really can’t remember what basic it’s from.
To translate the sibling, the third one is where it would tell you how dangerous the substance is for you. But it’s keeping its secrets.
And now interplanetary percussive maintenance is a thing too.
You’d be surprised.
But seriously, numbers can be used as booleans in an impressive number of languages. Including machine code for almost every machine out there.
It’s called “shut up and calculate”
Besides, the waterfall style is that you get the perfect car… eventually… or rather, tomorrow, tomorrow you read this again and check if it’s the day you’ll get your car.
Nope. The requirements were always the same, and you are as far from them right now as you were at the beginning.
At this point, you are better inventing another name and publishing your branch as a new piece of software.
Oh, cool. I didn’t know about this one.
Trying Zed now on the eternal quest of eventually replacing emacs…
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?
The restaurant has exactly the average quality of everybody that cooks.
Not of restaurant chefs or people good at cooking. Everybody that cooks.