There are clearly more to know. But this is a good list already.

Some tips which are easily forgotten to get the most out of std::vector.

This is a nice little experiment. Not statistically relevant (there are other papers for that), but shows in the details how introducing Rust can impact the way people work. This is interesting because it means the safety gains are not only strictly coming from the (now infamous) borrow checker. We can't rely on everyone applying all the techniques necessary but for sure they're cheaper to put in place than with C.

The concept of allocators in general and arena allocators in particular is too little know. Here is a little article which rediscover the motives behind them. It's a good introduction to the topic.

Good list of interesting features in Python. Some are tied to the gradual typing system but not all of them. Definitely tricks to keep in your bag.

A new type of strings to keep an eye on in the upcoming Python release.

A few interesting tricks to apply to Java code. Some I already did, but the proposed model for algebraic data types I might add to my bag of tricks.

The language keeps evolving, this is a good reminder that some old idiom can be let go. Parameter packs still need some adjustments to become nicer though.

A bit of a self-serving post towards the end. Still I like it because it clearly mention that it's not about dropping all documentation in favor of the code (quite the contrary in fact, documentation is very much needed). It really is about treating code like documentation, putting the same care into it in terms of readability and understandability. If you wonder what code reviews are for... it's also for this readability concern.

A list of opinions on our field. It's personal and biased of course, so make that you want out of it. I agree with most I'd say. A couple are rather niche though.

Sure, you get good memory safety with Rust. It's important and welcome, but it's just the beginning of the story.

A friendly reminder that Javascript is an endless pit of surprising behaviors. Watch out!

For sure the aforementioned manager need to fix his communication style. That being said the core advice was indeed good.

Or why analogies with physical work don't work...

Again that confirms that all the hype and grand announcements are not deserved. It also gives a good idea of the skills which are required to use those tools, clearly the setup process is involved if you want to don't want to be overwhelmed and drowning in bad code.

Despite the marketing speak... it's definitely not there yet. So far all the attempts at using LLM for coding larger pieces end up in this kind of messy results. It helps kickstarting a project indeed but quickly degenerates after that.

Indeed, it's something where we lack consensus across languages and sometimes within the same ecosystem.

Definitely ugly in the end. Still it does the the trick.

With the little Go I wrote, I admit that the multiple return values feature is... odd. Worse though, it has bad ramifications.

The whole field is unfortunately a bit fuzzy. That said, this article gives interesting ideas about what to pay attention to when writing code to ease the readability.