Very nice editorial. It's clear that the level of trust in the technologies we depend on is low... but that's not due to the technologies themselves it's more about the business practices around them. In the end the solution will have to be political, in the meantime we ought to support the good players.

Yet another attempt at protecting content from AI scrapers. A very different approach for this one.

Pointing out an important dilemma indeed. Which tests to keep over time? What to do with redundancies?

It becomes clear that there are more and more reasons to move back to simpler times regarding the handling of web frontends.

There was a time when scraping bots were well behaved... Now apparently we have to add software to actively defend against AI scrapers.

Really cool procedural environment generation.

I think this is a very welcome protest at FOSDEM. This keynote would be a shame on the conference. Unfortunately I already planned to not attend FOSDEM this year, but if you are: please participate to this sit-in.

Looks like a really nice tool to work with systemd services. It also integrates with my trusty lnav for the journal handling. I'll definitely give it a try going forward.

This article is feature packed, lots of great ideas to exploit git trailers. This can help automate some workflows easily.

You like RSS feeds? Ask for them!

A nice extension for Postgres allowing to ease the protection of personal information.

Nice trick for cleaner interruptible python scripts indeed.

Interesting article. There's clearly space for both languages indeed. They'll end up having each their own ecological niches, probably with some overlap.

A bit long and a bit too much framed in a "vs Python" fashion for my taste. That said it contains good advice on how to prototype or start simple with Rust. It's aligned with some of the advice I give as well. People tend to turn to low level details too quickly forcing themselves into a corner. There are better ways to handle it.

Color perception keeps being a fascinating and difficult topic.

Stuck in a state you don't like with Git? Here is a list of funny recipes.

Or why it can be dangerous to label medium the high likelihood low impact risks and the low likelihood high impact ones. One category is to be completely avoided while the other brings learning opportunities.

Or why you can't consider risks in isolation. It's too often forgotten.

This is definitely an excellent use of robotics. Probably one of the best I've seen. The things we can do when we're not just focusing on increasing productivity. These people get a shared sense of belonging they'd have a hard time to have without those robots.

Interesting extra dimension to think about risks. I don't think I ever encountered it in the wild but that can make sense to use it.