Yet another article about Postgres full test search features. This one has the advantage of giving us a glimpse about the other available options. Sometimes you want something typo resistant for instance.

Interesting position from AMD regarding the race on the next super computers. They're all being caught up by energy efficiency so it'll need to be addressed both at the processor architecture level but also at the software architecture level. How we design our computing tasks will matter more and more.

Excellent response to an article full of misconceptions about the Agile approaches. This turns in a good summary of cargo cult agile we see in the wild and the original intent. I especially like how it points out approaches to properly integrate UX as well.

I think it's the single one reason which makes Kotlin tempting to me every time I dabble in the Java ecosystem.

Or why they are definitely not a magic tool for programming. Far from it. This might help developers a tiny bit, at the expense of killing the learning of students falling for it and the creation of a massive amount of low quality content.

This is actually an interesting feature to know when a key changes.

Interesting to see the beginning of Kent Beck's thinking about scaling Extreme Programming. This was clearly missing. First by looking at dependencies which are definitely a problem which arises quickly at scale.

Looks like an interesting tool for scripting refactorings. Seems lightweight and more forgiving than Semgrep, looks like there's space for both in our tool belts.

Excellent piece as usual from Cory Doctorow. It quite clearly point out why Google is anxious and running off the chatbot cliff

YAGNI is one of the easiest to misunderstood ideas behind eXtreme Programming. That's why I think it's a good thing it stays under active discussion. Often people understand it too literally which can create issues. That's why people talking about "PAGNI" (probably are gonna need it) are right. After all, people who also conceptualized YAGNI wrote back then: "This doesn't mean you should avoid building flexibility into your code".

Interesting strategy, shows a fascinating blind spot in the typical AIs used for Go nowadays. It kind of hints to the fact that the neural networks abstract knowledge much less than advertised.

It is indeed getting easier every days to self host a website. Some other services or email are a different story though.

Interesting explanations of the main drawbacks of microservices. Nothing is magical so you need to know what you loose, in this case this is mostly about increased coordination efforts and latency in feature availability.

Admittedly biased thought experiment but there's definitely some truth in there. Focusing on the impact of what you release is way more important than focusing on releasing lots of features.

Inaccuracies, contradicting itself, conflating events, misquoting sources... all of that mixed with some correct facts, it's a perfect misinformation spreading machine. This just can't be trusted at this point. Those experiments should be stopped in my opinion, better do proper homeworks first, then relaunch when this can be better trusted.

Interesting approach. There's still a lot we can achieve with static analysis in those good old languages.

To me that looks like a fine advice even outside of C++. If conditions get at least a bit complex moving them out of the if to assign them to const booleans is always a good idea.

Interesting set of tools for displaying maps and managing their tiles.

Interesting move. Looks like Java will get value types at last. Coming from C++ this feels long overdue.

Indeed people still seem to assume Mastodon is just a Twitter clone. This is a good reminder that it's not, it's just one front to the Fediverse and that's much more interesting than a Twitter clone.