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.

Good refresher about linear algebra. I see it so underused in projects that really we need good resources to embark people into using linear algebra more.

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.

This stresses how important to put specific procedures in place regarding remote workers. It's in particular essential to have emergency contacts on both sides.

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.

You think you don't use power on others? Think again, this can be more subtle than you think. Keep it in mind, be mindful and try to use your advantages fairly.

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.

Nice higher level view of how a codec like H.264 works. Not really dive in the intricate details specific to H.264 though.

Looks like a very good resource about PBR.

This is a welcome and necessary clarification. Now there is a court decision clarifying what using the "Commons Clause" mean.

Very good reminder that as an industry we're quick to blame external factors for our own failures. Of course we can be given a bad hand, but sometimes we'd have failed with a good hand as well.