More discussion about models collapse. The provenance of data will become a crucial factor to our ability to train further models.

Still not perfect, but that's an interesting development.

Content creators are clearly annoyed at the lack of consent. The more technical ones are trying to take the matter in their own hands.

Make sure to read also part 2. You'd expect critical infrastructure like this to not be exposed over the Internet, and to be properly protected...

There's a good reason to have it in the standard. As mentioned in this post it can help with std::variant.

This can definitely come in handy. I can see myself using it for testing behaviors in the past or the future on a real application. This should also help writing automated tests in some cases.

This is indeed a shame. It'd be nice to not add all the concepts you plan on supporting in the class declaration...

The cleanup of that mess is still on-going. A bit more automation would help.

It's a piece which really resonates with me. I've been thinking and saying for a while that focusing mostly on the technical (licensing and dev) aspects of Open Source was a mistake. This completely overlooked the political side of the Free Software equation. This is why the industry is as it is now. We need stronger commons and indeed the AGPL is best for that.

Need to make a realtime collaboration application? This might come in handy.

Interesting preprint review. Not sure I got it all in depth, will definitely need to revisit it at some point.

Some improvements coming in SQLite transactions. Here are some early tests.

Three good advices on writing automated tests. This is necessary but not sufficient though.

Where are the limitations of using SQLite in production for web applications? Here is a good list.

Definitely this. C++ isn't going away anytime soon. Rewrites won't be worth it in important cases, so improving the safety of the language matters.

A bit long and a couple of mistakes when pointing out the flaws of story points. Still, it's definitely a worthwhile read. Quite a lot of the criticism of story points is warranted and the proposed approach based on queue theory is welcome. This is stuff you can find in Kanban like approaches and mature XP.

Django doesn't always generate the migration you'd expect. Read them before going to production. Also it's fine to adjust them.

Or examples of the collapse of a shared reality. This has nothing to do with "social" media anymore. Very nice investigation in any case.

This is indeed a problem. Somehow it became much harder to attract younger developers.

Quite a few good lessons in there. Again it's more about social skills than technical skills.