Long and nice article about collaborative editing algorithms and their implementation. The problem space is tough, benchmarking is hard, profiling as well and optimizing even more so. Very thorough.

Good reminder of the limits of machine learning. There's no clear path from machine learning to more general intelligence. This article doesn't account for emergence effects though. They are a possibility but that's a long stretch from what being exhibited so far: it's "just" statistics.

This is a bad trend. One needs a properly setup space for remote work. This obviously raises questions of real estate and money. I wonder how far employers would go to support remote working there... Buying a chair might not be enough.

Interesting guide on how to make the design of your frontend "eco friendly". Lots of tips in there on how to spare bandwidth and CPU time for the reader. Tends to push toward more minimalist designs which I definitely like. :-)

Good reminder of why if you got mobile devices which are outside of a secured office (like most companies nowadays) you should never underestimate the Evil-Maid scenario...

Now that finally looks like an interesting approach to make GPU computation more accessible to the public. This seems to do a few things right to lower a bit the complexity while retaining good performances.

Nice extracts with comments about finding joy in your (work) life or not. Two paths really... which one are you on?

Too bad this is stretching a bit too far on the politics side (although it's not unjustified, I think it muddies the initial message in this context).

A good primer on full-text search features in Postgres. A nice way to get started. This is too often overlooked, you can wait before pulling another dependency like Elasticsearch.

A very interesting look at the history of the Agile movement. What it really meant and what it degenerated into.

A very thorough resource on how the Python import system works. Very convenient to figure out what's broken when something goes wrong.

Ah! I thought this was often a missing piece in most React frontend code I've seen which mostly piles up useEffect and useState calls. Having a finite state machine is definitely a must have there, I'm glad some options actually exist, I didn't bump into XState so far I'll make sure to look into it.

Looks like an interesting tool, it's always a bit of a problem to simulate various network conditions, especially slow links randomly dropping packets. Adding more tooling to tackle this is always welcome.

The journey of Rust inside of the Linux kernel is still in its early days. I find especially interesting the questions raised by the community. It's especially healthy in my opinion, it's not just "fancy let's have it". They also wonder about the learning path for people to join the community if it's accepted or where to best use it. It's a good account of the social aspects triggered by technical changes.

Nice piece advocating for self hosting. I especially like the fact that it stresses that it doesn't mean "one server for one person" it'd be unrealistic to turn everyone into sysadmins.

Looks like an interesting system to recognize bird sounds in the wild. I'll definitely test it.

I think this is the best analysis about GitHub Copilot so far. Clearly using it in production today carries lots of risks. It might improve in the future but only marginally and likely with quite some effort. Not sure it'll pass the threshold to be anything else than a funny toy.

It's a very nice paper on spreadsheets and how we use them. It got enough history in it to make me tick (goes back all the way to the 1300s!). Also it's well balanced, it's not just about blindly blaming tools but looks at their shortcomings but also how we often use the wrong tool for the task... and then end up managing data and knowledge really badly.

Now that looks like a very interesting modular laptop. I'd be interested to test it and would love to see some KDE stuff installed on it by default. ;-)

Nice comprehensive list of the smart pointer types in Rust.

This is a sane approach and a good list of steps for estimating at large scale.