Very Rust focused, still it's an interesting debate. It gives a good overview of the different types of lock behaviors in case of failures. It's very much advocating for the poisoning approach which is indeed an interesting one (coming with its own tradeoffs of course).

I agree with most of the points here. They make all the difference. The audio is too often underestimated.

Some areas of our industry are more prone to the "fashion of the day" madness than others. Still there's indeed some potential decay in what we learn, what matters is finding and focusing on what will last.

An old one and a bit all over the place. Still, plenty of interesting advice and insights.

A bit too high on the "positive caricature scale" to my taste. That said there's a kernel of truth there, focusing on the developer experience will lead to improved impact.

Shows that you don't always need to put stuff in Box to get dynamic dispatch.

Another illustration of how to use a new type to declare intent for display of values.

Or why it's important to mentor others and not stay in your own bubble.

This is a good way to see that the architecture questions are multi-layered. And yes, in enterprise contexts they go all the way to the company strategy level.

IDEs allowing to spawn actions in the user environment are still a big security risk.

This needs repeating but yes, quality matters in test code too.

Lots of good advice for better interviews. I like the structure it brings making sure you got balanced evidences.

Decades that our industry doesn't improve its track record. But there are real consequences for users. Some more ethics would be welcome in our profession.

This is getting more and more accessible. It's also one of the uses which makes sense for LLMs.

This is a nice application level sandboxing feature on Linux. We should probably have more applications use it.

I don't even get why this became a topic of conversation but here we go. At least this thought experiment is a good way to learn about electronics in space.

Looks like a nice kit to add to your tool belt. Does some handy checks if you have a Postgres database to manage.

Unsurprisingly the big tech players want their own information bubble too. This kind of propaganda machine isn't really new, but they feel like they need their own now.

This kind of migration is apparently easier than it sounds.

Definitely fun research. Let's not be fooled though it also has practical use.