Indeed a good reminder that TDD might not be possible to properly apply at the physical boundaries of the system.

If you're asked a broad project estimate, building a very fine grained user story list is likely not the best approach.

This is funny how this article written a long while ago now is still relevant... These are all good reasons for reading Kent Beck's book about XP.

Struggling with TDD? Really feel like you need to write the implementation first? This is a fine approach. One caveat though, you have to be very disciplined in the way you uncomment the code, otherwise you'll quickly loose the benefits.

Maybe something good will come out of the political turmoil around the CVE Program. This would be nice to see it more independent indeed.

They keep being fascinating to me. Nice reflections showing how they can impact regular systems as well. I wonder why OCaml seems to be so prevalent in that space though.

I willadmit it... I laughed. And that's just one business risk among many.

Interesting architectural proposal for highly portable C++ based libraries.

This model is probably still a better one than certifications or very heavy processes. Far from perfect of course, but at least it gives a compass to teams to see if they're going in the right direction.

If you forgot that the memory allocator can matter greatly depending on your workload.

Nice little comparison of raw loops and ranges in C++. As always, measure before making assumptions... Unsurprisingly it ends up on the usual readability vs performance debate.

You like having surveillance camera roaming around town? Well, you're covered...

A few interesting tricks to apply to Java code. Some I already did, but the proposed model for algebraic data types I might add to my bag of tricks.

Very nice deep dive into the reasoning behind a wavy gradient effect. It shows the best effect have several layers of refinements and tricks. Each trick is explained separately nicely, this is a good read.

Nice trick for highly performance sensitive data structures. Making data CPU local instead of thread local you can make a mechanism which is especially cache friendly.

This is a question which I have been pondering for a while... what will be left when the generative AI bursts. And indeed it won't be the models as they won't age well. The conclusion of this article got a chill running down my spine. It's indeed likely that the conclusion will be infrastructure for a bigger surveillance apparatus.

Looks like a nice resource for CMake. The documentation for it isn't always great especially for beginners, hopefully it should fill that gap.

Sourcehut pulled the trigger on their crawler deterrent. Good move, good explanations of the reasons too.

Nice little exercise to quickly figure out if the skillset of a team properly matches their project.

Writing shell scripts is still a craft. Interesting traps are presented here. Also, now better have shellcheck around for any non trivial script.