We got this nice feature a while ago now. It deserved to be used more, and it keeps improving.

Nice chapter to better understand Rust dyn traits (also called trait objects).

This is a widespread syndrome. It's not only in our industry of course but has real consequences in terms of leadership.

Yes, this one feature in the standard doesn't seem to reap much benefits... It's sad that it got there.

Databases do improve and provide more "cache like" features, but such caches are still needed for the time being.

A good reminder to use std::exchange more. Years after it's been introduced it's clearly still underused.

It's indeed quite possible to sneak in some symbols even in capture less lambdas. It all makes sense in the end.

A short and to the point reminder on how to manage properly a "layer cake" architecture.

It's been around for a long while now. This is an interesting way to complete the software craftsmanship view which didn't quite capture the "living ecosystem" side of our field.

Due to the strict type system this kind of conversion is not necessarily a given. There are ways though, and you can even keep it performing well.

A little article about a different type of grids for strategy games. Some of the consequences are very interesting.

Nice and clear indicators of how decentralized the fediverse and the "atmosphere" really are.

This is already an old article now. Still the core of it still rings true. The optimistic note at the end of it didn't come to pass though.

Good reminder of this important but imperfect guide to software design. There is some ambiguity on what "simplest" actually means. Still it helps keeping in mind that simple is rarely easy to find.

We got many options nowadays. Most of them are likely better than just making the underline disappear on links.

This is indeed an area which could be better handled in SQLite. It needs to be carefully checked when introduced in a project.

The idea is interesting... Seeing how the search engine space is degrading quickly I'm tempted to try this actually.

It's indeed a nice little pattern to use when the type system allows for exhaustiveness checks of destructure operations. Allows to gracefully handle extension of structs in the future.

Clearly Citrix is drowning as a product... How can people still trust the provider after such an episode?

This stays true, most projects are maintained by a single person and that's a problem. Where is the support from all the businesses benefiting from FOSS?