The trend keep being the same... And when the newer models will be trained on FOSS code which degraded in quality due to the use of the previous generation of models, things are going to get "interesting".

OK, this is old so I wish it'd go beyond 2003. Still, that's quite a funny read.

Gives an idea of what pair programming looks like when practiced properly.

I'm not really a fan of the leaderboard part of their approach. That said, if the maturity of the organisation allows it, having such bug squashing sessions is a good idea.

Ever wondered if we could solve the Fizz Buzz with a Fourier series? Trigonometry is magic.

Depending on the ecosystem it's more or less easy indeed. Let's remember that error handling is one of the hard problems to solve.

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

Neat stories explaining those three important features of Python.

Indeed it is. It's not the perfect or most sexy language, and yet it has some interesting properties.

Ver much biased of course. Still it's a good way to see how much Java evolved over time.

Interesting talk. The tools presented can indeed go a long way helping people figure out what's wrong with a piece of code or learning some of the harder parts of a language.

Feeling blocked? Maybe try a few of those things on your project.

Indeed, let's not fall for the marketing. It's better to write less code if it's enough to solve actual problems.

A bit of a long read, but does a good job explaining the use of assertions and how to introduce them in your organization.

That's an interesting trick to make sure people reevaluate comments when they remove some code. Doesn't work for every language of course.

Those principles are old now, but they really captured the zeitgeist of the time.

The example is maybe a bit on the simplistic side. Still it helps understand why you need to pay attention to the SRP.

This is still a valid approach. I regularly encounter cases where the type tag pattern would have been welcome.

This is still a good framework to think about what motivate developers in a team. Not everyone is the same.

A talk from Casey Muratori who is pushing his ideas on software architecture. This one is very interesting on the long history detour it does. Shows well how we keep rediscovering stuff which sometimes go back to the early times of computer science.