That sounds like a very interesting tool to simulate and test potential data loss scenarios. This is generally a bit difficult to do, should make it easier.

Politics in the Linux kernel can indeed be tough. The alternative path proposed to the Rust-for-Linux team is indeed an interesting one, it could bear interesting results quickly.

Good set of advices. I wish more people applying for a job would follow them.

Lots of things to keep in mind when dealing with databases. This is a nice list of "must know" for developers, false assumptions are widespread (and I fall in some of those traps myself from time to time).

This is really bad news... Clearly the publishers cartel would try to outlaw libraries if they were invented today.

Interesting view about the LSP specification, where it shines, and where it falls short.

Indeed this is a much better visualization. It shows quite well how the Python programmers pool is growing.

Good set of advices on naming variables, types, etc. Indeed this makes things easier to find in code bases.

An old article but a good reminder: you have to choose between latency and throughput, you can't have both in the same system.

There, now this seems like a real thing... your phone recording you while you're not aware for advertisement purposes. Nice surveillance apparatus. Thanks but no thanks.

Aligning people with differing core values in a team is indeed necessary but difficult. It can kill your project for small teams, for larger teams you will likely need to think your organization keeping the misalignment in mind.

Very good article. I wish I'd see more organisations writing such design documents. They help a lot, and that allows to have a way to track changes in the design. To me it's part of the minimal set of documentation you'd want on any non trivial project.

Does a good job listing the main myths the marketing around generative AI is built on. Don't fall for the marketing, exert critical thinking and rely on real properties of those systems.

An excellent essay about generative AI and art. Goes deep in the topic and explains very well how you can hardly make art with those tools. It's just too remote from how they work. I also particularly like the distinction between skill and intelligence. Indeed, we can make highly skilled but not intelligent systems using this technology.

Interesting point. As the memory safety of our APIs will increase, can we reduce the amount of sandboxing we need? This will never remove completely the need if only for logic bugs, but surely we could become more strategic about it.

Woops, this was clearly a very bad security issue allowing to completely bypass airport security screening in the US.

Interesting reason which would explain the Selenium flakiness. It's just harder to write tests with race conditions using Playwright.

It's about time... I wish they would have gone for the AGPL + proprietary double license scheme instead of their odd licenses the last time.

A weird detour via baseball obscure rules to justify why we should pay attention to the "Highlander problem". This should be kept in mind especially for designing databases.

Definitely a good advice, I see very complex expressions in if (or while BTW) conditions way too often. They tend to accumulate over time.