A little introductory article about putting an ATDD cycle in place for your development.

An interesting way to approach the topic of GPU programming nowadays. It might indeed make more sense nowadays than reaching for putting pixels on screen as a first objective.

As usual, you need to measure before you jump to conclusion...

Interesting idea, trying to bridge the best of both UUID options.

ETH Zurich keeps making progress on its model. It's exciting and nice to see an ethical offering develop in that space. It shows that when there is political will it can be treated as proper infrastructure.

Interesting take. Indeed risks shouldn't be considered in isolation. They actually compound and that can add up fairly quickly.

Another nice one about the power of RSS and why it's an important technology.

Interesting post which gives plenty of insights on how async Rust is designed and behaves.

Interesting breakdown of a possible organisation for accessing self-hosted hardware at home through wireguard.

Excellent profile of Tim Berners-Lee.

Go and read it! It'll give a lively impression of the Web early history. It's amazing how, back then, he managed to fend of the greed of corporate interests in order to make sure his original vision would survive. Of course not everything materialized, most notably the Semantic Web (sadly).

Nowadays, the real question is the fragmentation due to the big closed platforms power grab and the political context. Can we still save the Web? For sure there's no clear path yet.

Or on the importance of being able to say "no". If you see something fishy, at least refuse to participate in it.

Good opinion piece, I wholeheartedly agree with the author on the topic. Like it or not, politics happen in organizations. Ignoring this fact is an enabler for bad decision making.

Indeed, most complaints against "Don't Repeat Yourself" (DRY) are really arguments against a strawman. Of course you can go wrong, it's like everything else it's about balance... reducing the DRY guideline to a caricature to get rid of it won't help.

Maybe a bit extreme as an example, but highlights quite well why you want to limit logic in tests as much as possible.

Your digital life is secure? Good... now is it really safe? Can you recover in case of a catastrophic event?

Early days but it looks like an interesting use of the t-strings introduced in Python 3.14.

With the latest rulings Google feel like the ecosystem might escape its grip... So they plan to tighten it.

I'm not fully aligned with all of this article. That said, it's an interesting way to frame the topic of how we're having to make tradeoffs all the time.

An old series of posts which highlights quite well why GitFlow can be a problem and that you likely want something simpler. Since I still find GitFlow often recommended as a knee-jerk reaction, this is a good article to have in hand.

Nice list of templates to use for better handling of engineering management in your organisation. Pick, choose and adapt what makes sense to the context.