Very thorough overview on how registers are used when you get closer to the hardware. Very good resource to use as reference.

Indeed, the times when we could pretend one was a superset of the other are long gone.

Very early days and still hackish to use but that's definitely big news for the Python ecosystem.

Nice poster. It's harder to classify programming languages than it sounds. This one is interesting.

Interesting approach. I did quite some of that but without really putting it together like this. It's a nice way to explain it.

Good article on when to use comments or not. Also gives a few tips on how to write them properly.

Need to update your Java knowledge because it evolved quite a bit? Here is a little list of the features to focus on.

I'm still doubtful about it but maybe I'm wrong so a counterpoint to my own opinions. Of course this is a purely productivity standpoint in here which overlooks my main concerns with how this is currently deployed and used.

I definitely used this trick from time to time. In the right context it definitely work. Leaving some easy mess on purpose is a good way to get back into a task the next day.

Well, this is a bit obscure but we have to know it's there somehow. Better not rely on it too much though.

There are nice mechanism in the Java type system nowadays to no rely on Optional all the time. This is a good reminder of the main alternative.

Interesting musing about a language size and how it evolves over time. There's clearly tension between making it too big and keeping it relevant to modern uses.

A good point... everybody should know at this point that delegation should be favor. So why do we keep turning to inheritance even in cases we shouldn't? Convenience and writing less code mainly. Unfortunately that leads to bugs more often than not.

Neat way to think about array indices, if it was widespread it would simplify a few things in documentations I think.

Development is and has to be a team sport indeed.

That's an interesting perspective. Rust definitely gets in the way of iterating quickly indeed which might be a problem to test ideas. Introducing it gradually later is thus a better path. That being said it doesn't always have a great story for mixing with other languages, there are a few tools to help, but nothing I've seen really used in the wild so far (this will probably come though).

Alright, that's an impressive set of tools they created to build their games. Lots of efforts went into this, very inspiring.

In praise of the little ideas and the small achievements. They are often overlooked but definitely needed.

Or why they are definitely not a magic tool for programming. Far from it. This might help developers a tiny bit, at the expense of killing the learning of students falling for it and the creation of a massive amount of low quality content.

To me that looks like a fine advice even outside of C++. If conditions get at least a bit complex moving them out of the if to assign them to const booleans is always a good idea.