Definitely a good advice, I see very complex expressions in if (or while BTW) conditions way too often. They tend to accumulate over time.

Interesting to see how far you can go preprocessing Python.

This is a good point. The DRY principle has value but the trick is finding the right time to apply it.

This is a very important distinction to keep in mind. It's one of those source of bad mistakes in C++.

This would definitely be a nice change to the Java language.

Ever wondered how attributes work in Python under the hood? Here is how.

An interesting Python construct to make iterators based on a simple function.

Not really Rust specific, this might be an interesting way to structure your code once async gets introduced. Should avoid some of the usual traps.

Obviously very opinionated. Still probably a nice list to pick from when making your own project specific coding guidelines.

Ever wondered how this operator is implemented in Rust? It's not that complicated.

It might not look like a lot from the outside, but "just implementation details" in fact hides quite some work and complexity.

That's what happens where references are half hidden in a language. You think each closure get a different copy but in fact they all refer to the same object.

Definitely a nice Python trick. Fairly elegant, I'll try to remember it.

Definitely this. In a world where LLM would actually be accurate and would never spit outright crappy code, programmers would still be needed. It'd mean spending less time writing but more time investigating and debugging the produced code.

Interesting research! Is reading code a math and logic task? Is it a language task? Well... it might be its own thing.

Good food for thought. Explains quite well the factors which impact software development.

Interesting take about the mantras often used in our profession. They shouldn't be treated as laws, but as proverbs carrying a piece of contextual wisdom. It's thus unsurprising that they tend to contradict each other. This contradiction should make us pause and think.

Well, maybe our profession will make a leap forward. If instead of drinking the generative AI cool aid, if we really get a whole cohort of programmers better at critical skills (ethical issues, being skeptical of their tools, testing, software design and debugging) it'll clearly be some progress. Let's hope we don't fall in the obvious pitfalls.

Since there's a clear tendency in the developers I meet to "extract at all costs", this is a good reminder that sometimes you need to inline the code first. This very often brings better clarity in the context of use. In turns this leads to a better final extraction.

Funny read, it has lots of good advice for starting up with Rust.