This is indeed too often overlooked. Producing a test list and picking the tests in the right order is definitely a crucial skill to practice TDD. It goes hand in hand with software design skills.

Nice balanced view on some of Rust characteristics. This is much less naive than some of the "Rust is great" posts out there.

Good analysis of the backdoor recently discovered in xz. Really a bad situation. Luckily it was probably detected before it could do any real damage. What's especially striking is the amount of patience it required, it's really been put in place over a long stretch of time to reduce chances of detection.

All good points. Can we improve? Sure. Does it means we do it bad? No. Just do it more when it makes sense.

Good exploration of the CPU architectures we have nowadays, and why the RISC vs CISC debate doesn't make sense anymore.

Wondering where some of the biases of AI models generating images come from? This is an excellent deep dive into one of the most successful data sets used to train said models. And they've been curated by... statistical models not humans. This unsurprisingly amplifies biases all the way to the final models.

This is an excellent piece, I highly recommend reading it.

Interesting debug tool for web frontend code. It'd be nice as a browser extension.

Of course documentation, especially one presenting the architecture, shouldn't be neglected. It takes time and skills of course.

This is about a Rust library but equally applies to any ecosystem which allows to easily pull a dependency. As soon as you pull them, you need to monitor their health for the sake of your own project.

Interesting, with the price hikes and bundles to come, we might indeed see a resurgence in physical media. It will stay niche for sure, but looks like demand is about to grow.

In which case you want one or the other? This is illustrated in the Rust case which has its own struggles, but the question applies more largely in my opinion.

Making your own allocator? This is definitely something to consider and measure.

Might be a good alternative to JSON in some cases.

Interesting study on the impact generative AI can have on people performances in business settings. There are a few nuggets in there. In particular anything related to problem solving people do worse with generative AI tools than without. And even worse than that when they've been trained (probably due to overconfidence). The place where it seems to help is for more creativity related tasks... at the individual level, but at the collective level creativity decreases due to homogenization. Definitely things to keep in mind.

Very interesting piece. The chances that it is another bubble are high. It's currently surviving on a lot of wishful thinking and hypothetical. This really feels like borrowed time... I wonder what useful will remain once it all collapses. Coding assistants are very likely to survive. Clearly there could be interesting uses in a more sober approach.

Good reminder that you want the diagnosis tools in place and working before you get an actual problem in production.

Interesting API for running subprocesses and interact with files.

Indeed, time to leave Redis behind in favor of Redict. It's not like one can expect new things to come out to such a project.

This is a worrying trend we see in law enforcement a bit everywhere. It's a bit too convenient to make such requests even though it is unconstitutional.

Those were nasty, good they've been patched already.