Clearly a list of concerns to keep an eye on for wider Matrix adoption. Clearly some basics are not covered still.

It's too often forgotten how much our culture is fragile. So many digital artifacts which could just vanish or not be readable anymore years from now.

Like it or not but PHP is indeed here to stay.

Some progress, still a long way to go.

Definitely this, the message is often coming across lacking nuance. TDD can help you towards good design, but it's not ensuring you'll have a good design.

This is really bad... it's way worse than I suspected. The car makers really need to change their practices. Go and sign the petition.

Indeed, these confusions are widespread. Even worse, they generally lead you away from actual productivity.

Newer language really have a hard time moving up in this ranking. Lots of inertia all around.

This is indeed a good thing to hide dependencies behind interfaces when it makes sense.

What's worse than a compiler bug? A processor one... very interesting deep dive in this particularly nasty one.

Interesting look at the challenges ahead for the fediverse. Not easy since some of this is cultural clash, some of it is technical and solvable though.

I think I'd have gone further in the past for such a thought experiment... still if you wonder why people are fighting for digital freedom, here is why.

Very welcome tool, well done as well.

Ever wonder how floppy disks worked? Here is your chance to find out, good reference.

A good proof that it's still possible to innovate with interesting performance gains for rather mundane tasks. If you're into calendars this is an interesting read.

A good reminder that you better measure the right thing... otherwise you might consider someone as unproductive while he has in fact a large impact.

Interesting and unfortunate security issue... This is admittedly a somewhat unusual setup though, but to be kept in mind I think.

First time I hear about this application. It seems really nice, I'm taking it for a spin. Not sure I'll use it to replace OsmAnd just yet. That said it's UX seems better than OsmAnd so far.

I'd take the more stack related side of this article with a pinch of salt. It seems a bit too specific to the company behind the story. The rest of the article rings true and spot on though.

Now this is actually an interesting and good use of the latest trend in large language models. You can simulate difficult conversations, getting more experience there can help.