Nice summary of everything you can do with operators overload in Python.

Interesting set of follow up questions during a retrospective.

Welcome in France, this country which claims to be a beacon for Human Rights but has a problem with its law enforcement for the past two centuries... surveillance abounds and its accelerating.

Indeed, we need more traffic going through Tor if we want to keep it effective.

This is well deserved. She's doing a very important work for the progress of science. All those pay walls are nonsense.

The FSF words are strong but deserved in this case. Let's hope it marks the beginning of an efficient campaign against this move from Google.

OK, this could be big for Python. Let's see how they execute this plan. It carries some risks as well, but they seem well aware of them.

Interesting to look at several career progression models and compare them indeed. This is likely necessary when making your own model for your context.

I was indeed thinking this looks awfully similar to some things we've seen in the past... It needs to be fought as well.

An excellent explanation of the Unicode standard, complete with a bit of history. This is a good resource.

There's a new player in the message queue space. This one looks interesting.

This is a good resource to learn Vim or if you want to get better at it.

More details and analysis about the events unfolding around the Google "Web Environment Integrity" proposal. This still doesn't bode well. Whatever they claim it seems clear it's about getting rid of ad-blockers.

Wise words. This is overall a good approach to add new components and behaviors to a system.

Can't say I learned much but that was a very neat refresher. It's very well done, so if you never dabbled in the basics of how the hardware or the kernel work I strongly recommend reading it.

Looks like an interesting extension for Postgres to do vector similarity searches inside the database.

Clearly the book referenced here picked my interest, I guess I'll try to read it. The cheat sheet proposed here is interesting, not completely sure how I'd act on it in practice though.

I think this is the right way to look at the problem space. The analysis provides the right pros and cons to look at when picking a frontend framework.

This is an interesting idea, I think I'll try it to see how it impacts my memory.

This apparently needs to be reminded from time to time. So here it is: don't expect those timestamps to be unique, even on a single machine.