This is maybe the property of tests which is the most easily misunderstood. It's not always easy to respect it as well.

Long but nice post about all the things you need to figure out about working with databases when the only thing you know is imperative languages.

Another nice use of the upcoming C++ reflection feature.

Interesting analysis of the crates ecosystem. It shows quite well some of the challenges and weaknesses. Nothing to worry about yet about the ecosystem health overall. Still, you should probably be careful when picking dependencies.

I didn't know about this project. This sounds interesting, smart use of mkosi to make an Incus tailored system.

A good list of code smells to pay attention to in Rust. Also provides patterns to avoid such smells.

Deceptive title! It's far from simple and the article confirms it. It's fascinating to see all the dimensions you have to deal with to design a game though.

The title is a bit misleading in a way (and I almost didn't click through for a start). That said, it is an interesting essay dealing with the topics of intelligence, problem solving etc. I'm not sure I agree with everything in it, but that's still good food for thought.

I admit I'm tempted to look at Typst more nowadays. It looks like it can simplify the production of content quite a bit compared to some of the good oldies we still carry around (like LaTeX). That said, Typst is still young and not that stable yet.

This is unfortunately still a bit complicated for my taste. Ideally std::simd should be stabilized, but since it's not the case yet options have to be evaluated.

A long needed improvement to Java on its way to the JDK. Looking forward to this one stabilizing.

The trend has been clear for a while. This is a well crafted job of clearly mapping it out. Time for Europe to wake up maybe?

Unfortunately and as far as I can tell we're still not there. I'm trying to do my part in how I push for those topics when working with teams and organizations. So many things to help with on the practice level and making developer teams function properly.

Nice little article to get an idea of the culture and art behind magic tricks.

An old introduction to DDD. Not necessarily the best reference on the topic (which is probably still the blue book). Probably a good resource to skim over the important points and get started though.

We can cast doubt on the "Spotify Model" (not really a model anyway...) all we want. Still, I think the whole "guild" idea in there was spot on. This article gives a feel of how it can be setup and the benefits it can bring.

A good reminder that you don't want your code base clean to the point of being sterile. You have to fight off the mess yes, but some of it can stay if it provides affordances.

Neat stories explaining those three important features of Python.

Indeed, if we weaken the learning loop by using coding assistants then we might feel we go faster while we're building up the maintenance cliff. We need to have an understanding of the system.

I use it mostly from the DAV integrations, so I don't notice this much in practice. That said, if and when I have to use the web GUI, it indeed always feel sluggish to me. There might be a reason behind it indeed, those bundles seem way off.