Very interesting piece... shows how someone can end up maintaining something essential for decades. This is a lesson for us all.

Good musing about major version numbers and backward compatibility. It is indeed important to communicate breaking changes properly and to not have those too often.

Indeed the analogy from "ultra-processed food" is an interesting one in the information context.

OK, this is a rant about the state of the market and people drinking kool-aid. A bit long but I found it funny and well deserved at times.

Ever wondered how this operator is implemented in Rust? It's not that complicated.

Why box plots are hard to grasp and probably badly designed. There are good alternatives out there though.

Interesting trick for a zip based format containing mostly text.

JSON, its grammar and the security implications. The approach of looking at a restricted subset is interesting.

It was already hard to trust this company, but now... that clearly gives an idea of the kind of monetization channels they're contemplating.

It might not look like a lot from the outside, but "just implementation details" in fact hides quite some work and complexity.

Very nice piece about the various types of complexities we encounter in our trade, and what we can or should do about it.

The creative ways to exfiltrate data from chat systems built with LLMs...

Very interesting move. I wish them well!

That's what happens where references are half hidden in a language. You think each closure get a different copy but in fact they all refer to the same object.

This is indeed a real concern... with no propre solution in sight.

This is a funny pretense, and yet... If any of this remind you of a real context, this would be paper cuts. Have enough of those and indeed the organization might grind to a halt.

Some problems are indeed tackled faster by having a simulation allowing to explore potential solutions. It's tempting to go very formal and theoretical but it'd require more effort and be more error prone.

This is indeed an easy mistake to do. It's better be avoided.

Since there are ways to offset the plagiarism a bit, let's do it. Obviously it's not perfect but that's a start.

Interesting dive into how join() and generator behave in CPython.