REPLicated2

> 3. Consistent lock ordering: avoiding deadlocks

This section is badly written. For example, it refers to different table names than those previously introduced.

The slop shows. While I appreciate the post, I wonder why they didn't bother using an LLM in a way that would at least ensure internal consistency.

Anecdote: When I was looking for a job in 2014, they were present at a student job fair in Zurich. Barely knowing that company, I started off the conversation with "hey, you are creating all these intelligence tools for governments, right?".

The representative somehow started rambling incoherently about what wonderful work they do for NGOs and non-profits. Without acknowledging that their main customers are the intelligence community and law enforcement. Or telling me anything concrete their software is supposed to achieve.

Color me not surprised. Needless to say, I applied for a supposedly much lower-paying job where I actually knew what the work was about.

I always liked the file syncing part of Dropbox, and was considering their Family plan a few years back, until they increased the prices. If I remember correctly, their reasoning included all the additional features like Paper which you would get but that I never needed. It's currently at 203 EUR/year here - pretty steep if you only care about the core usecase of syncing files.

Depending on your viewpoint, this may actually be a boon for reverse engineering efforts to counter planned obsolescence.

When I started dabbling in electronics recently, I ran into switch bouncing apparently as I used a push button to generate the "clock" input of a CD4017 decade counter and it showed rather erratic output behavior.

Adding a capacitor fixed it. Which reminds me that I should really invest in an oscilloscope to validate my (not so) educated guesses.

Great resource to read up on this topic, thanks.