Definitely a good list of advices for first time contributors.
Interesting explanation of a research paper exploring the possibility of a faster SQLite by focusing on async I/O.
A good question, it is somewhat of a grey area at times. We need to come up with better answers.
Interesting ideas about leadership lacking in impact. Indeed it should be seen as a communal function, it's not about individuals leading each in their own directions. Think about it in a systemic way.
Yet another long piece in this interesting and in depth conversation about Bluesky. The fact that it stays civil is called out explicitly and this is appreciated.
Good list of the undocumented rules terminal programs tend to follow. It's nice to have this kind of consistency even though a bit by accident.
Nice little systemd trick, definitely an alias to add to your setup.
Excellent post showing all the nuances of AI skepticism. Can you find in which category you are? I definitely match several of them.
JSON is full of pitfalls. Here is a good summary. Still it is very widespread.
Jujutsu is indeed alluring... but its long term support is questionable, that's what keeps me away from it for now.
Looks like a nice model to produce 3D assets. Should speed up a bit the work of artists for producing background elements, I guess there will be manual adjustments needed in the end still.
This is indeed a nice template for submitting changes for review. It's very thorough and helps reviewers.
A good summary on the various concepts needed to reason about time.
The idea is interesting even though it probably needs to mature. It's interesting to see this kind of libraries popup though, there's clearly some kind of "backend - frontend split" fatigue going on.
A single tool to manage your environment and dev tools across projects? Seems a bit young and needs a proper community still. I'm surely tempted to give it a spin though.
Interesting JSON superset which makes it more usable for humans. I wonder if it'll see more parsers appear.
Interesting report, some findings are kind of unexpected. It's interesting to see how much npm and maven dominate the supply chain. Clearly there's a need for a global scheme to identify dependencies, hopefully we'll get there.
A very precious document. Shows great organization in the work of Knuth of course but the self-reflection has profound lessons pertaining to estimates, type of errors we make, etc.
We're still struggling about how to modularize our code. Sometimes we should go back to the basics, this paper by Parnas from 1972 basically gave us the code insights needs to modularize programs properly.
An old one now, but since I keep giving this advice it seems relevant still. If you're using raw loops at least that no again, there is likely a good alternative in the STL.