It's all written oriented toward C++ use. That said I think most of it equally applies whatever the language.

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".

This needs repeating but yes, quality matters in test code too.

Decades that our industry doesn't improve its track record. But there are real consequences for users. Some more ethics would be welcome in our profession.

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.

Didn't know about that clippy feature. This is neat, allows to precisely target some of your project rules.

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

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.

An interesting set of principles for code reviews.

An explanation about where the SRP comes from and what it really means. It's very often misunderstood or overlooked.

I'm not fully aligned with all of this article. That said, it's an interesting way to frame the topic of how we're having to make tradeoffs all the time.

Easy to misunderstand as an elitist stance... But it's not the way I read it. Churning more code faster isn't going to help us, you need to take the time for people to grow and improve. It's not possible to achieve if you're drowning in eager beginners.

A good reminder that long hours are not a sign of success with your project... on the contrary.

There's a big "if" of course, don't just throw your tests out of the window. But indeed, they need to bring value... so start by having really good tests.

A good explanation of why the concept is important, also comes with a nice list to get started.

The question is always valid. I like this particular answer.

A short list of common code smells that people need to know.

Both approaches have their pros and cons of course. Whatever you pick, it has to start with a care for quality shared within the team.

Definitely this, too often I see projects treating the technical debt as one-off large tasks. Really it's something you should deal with bite sized and over time.

I don't think I'm ready to give up just yet... Still, I recognise myself so much in this piece it feels like I could have written it (alas I don't write as well).