Metaluim

Well, the pelican benchmark is easily verifiable.

Well, not officially, but there are solutions for that. Like BDR (or Postgres Distributed nowadays) by EDB.

You do realise this is your experience, and just outs you as a mediocre engineer and doesn't prove that slow and steady doesn't win the race, right?

Or did you write your comment with an intentional self-demeaning note, and not a sarcastic tone?

It's funny - I was just thinking about your book club earlier this morning. Found some good recommendations over there!

So much for redundancy I guess.

I do something similar to your first approach just as I'm about to context switch (either because the day has ended or I have to work on something else).

I write a small summary of what I was doing and what were my next steps at the time, and I write this either directly in the code, in paper or sometimes in a text file. I call them ENDSNAPs (end snapshots).

But the model you mentioned also doesn't work, because it's essentially single-task, IIUC.

Now all I need is for wages to be actually attractive in Lisbon, given the rising rents.

Quiver is a startup developing a cloud storage platform, similar to Dropbox with additional protection and tracking over file usage. Quiver allows a user to share a file with other users and enforce various protections on it, such as a validation expiry date, read-only, geolocation based usage, etc...

There's literally only a room