Good list of interesting CLI tools. I adopted quite a few of them, there are more I'd like to evaluate.

Funny experiment, that's a seriously small docker image now!

This is a good example in my opinion: stick with simple choices as long as possible, invest the complexity where it matters.

Interesting use of Rust behind a Python API. This is IMO an interesting niche for the language.

Nice list of lesser known tricks with Python formatted string literals.

OK, definitely not something I'd advise by default. Still, if you're in the right situation that might be an option. The fact that they don't deploy in one go is definitely a factor here.

OK... now that's really neat for most teaching situations. I want one. :-)

The never ending debate on the tools used to produce free software. Of course, in general those tools should be free software as well (IMHO).

Admittedly, the go toolchain seems to handle supply chain problems in a neat way. I especially like the VCS as the source of truth.

I like the noise metaphor it briefly mentions. It's indeed similar, you're within constant noise, you don't notice it anymore but still when it stops you feel relieved. The benefits listed are indeed to be expected.

OK, that's indeed an easy mistake to make with docker and how it uses OverlayFS.

Interesting way to see where to spend time in reviews.

This article is spot on in my opinion. This resonates so much with my own experience and ethos... I guess I could have written that if my prose was any good.

Interesting paper, shows a surprisingly large percentage of jobs doable from home. Also shows that the frontier between doable or not seems to be at least partly related to inequalities. If you already have high wages, you got higher chances of having the privilege to work from home.

This sounds like it could be a game changer for some uses including robotics or XR. Will need to look at this deeper.

Very interesting initiatives... I wonder what they will lead to legal wise.

Now that's an interesting idea to give back money to maintainers... can be sustainable only if enough company do this on a regular basis though.

Interesting list of criteria about why you might not use some piece of tech. Also delves into why this is often not public knowledge.

Bunch of good advice. In a way it boils down to: name things properly and use static analysis tools extensively. Still, couple of nice operational guidelines which work in most languages.

Interesting tip to ease the pain of dealing with HTTPs when using Wireshark.