Might come in handy when Filelight is not available, I could see myself using this over SSH connections.
Interesting way to organize your data. This gives a library feel for sure. At least it makes me curious.
Interesting idea, personas help with producing features, something is needed to prevent features we don't wante.
Interesting feature from the Python language. Lots of features are actually built on top of it.
Interesting and provoking thought... Indeed it's hard to build communities while also aiming for rapid and constant growth. There's no chance of having communities properly stabilize which leads to the tribalism and bad behavior we see on social media.
Interesting ideas for using large language models. There is a world beyond the chatbot interface and it might bring more value to users and avoid some of the pitfalls of anthropomorphisation.
Signature of digital documents is definitely not as safe as we would like. All the serious formats have known flaws at this point.
Interesting experiment... with surprising results in places. What stays available or not is not necessarily what one would think. It's not that easy to be flexible and available across regions.
Funny list of anti-patterns. Not all of it is C++ specific in there, but some are good reminders of the hidden traps in the language.
Very interesting study on dependencies. This is specific to the Maven ecosystem so too early to generalize the findings to other similar ecosystems. This indicates at least the difficulties of managing dependencies, especially the transitive ones. Also tries to define the "dependencies bloat" problem.
Good piece on how to reduce uncertainty before something is built and ready to be in front of users. It starts with prototyping but goes all the way to feature flags and deployment
Things improved a bit... they also got worse in a way. This stays an ongoing fight for the years to come.
Interesting little tool, can come in handy.
The interview is overall very interesting (I advise listening to it in full). It's nice to have such an historical perspective. At 15:00 there's a question which prompt a very important explanation of why the word "over" was chosen and repeated in the agile manifesto. Unfortunately it's been often misinterpreted...
A piece criticizing the asyncio approach in Python (especially considering the performance tradeoffs in this language). Also provides viable alternatives.
Deep dive on a proper benchmarking and implementation for 1M task on the Erlang runtime. Clearly the previous benchmark had room for improvements.
Nice piece which shows how easy it is to get such models to produce nonsense.
A good reminder that Flatpak is no silver bullet. It's a bit of a rant at times still it has some good points in particular the security implications are not always properly conveyed to the users. Some thinking might be required regarding what's lost compared to "traditional" packaging approaches.
Very interesting case full of lessons. Of course, increasing the complexity of the system overall can lead to such hard to find issues. It's also a tale into how seemingly innocuous settings can interact in unexpected ways. I also like the lessons learn pointing to the fact that you can and should debug even the systems you use through abstractions, diving into the code is almost always a good thing (even if in this particular case it wasn't strictly necessary in the end). And last but not least it shows the tension between mastery and automation... the more you automate the least you master the system, and at the same time this automation is necessary for building resilience in the system.
There's a new grep alternative in town. Looks really fast and has an interesting interactive mode. Definitely something to check out.