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.
Nice tutorial for rendering water. It gets more complex from there but this one is doing quite a lot already.
How to get started with putting in place an Agile approach in a team? Clearly structure helps in the beginning. One caveat of the article though: don't read this as having to respect a book to the letter forever, it's merely a starting point.
A good tour of the important HTTP headers.
This matches what I see. For some tasks these can be helpful tools, but it definitely need a strong hand to steer them in the right direction and to know when to not use them. If you're a junior you'd better invest in the craft rather than such tools. If you got experience, use with care and keep the ethical conundrum in mind.
The language keeps evolving, this is a good reminder that some old idiom can be let go. Parameter packs still need some adjustments to become nicer though.
Don't confuse scenarios for predictions... Big climate improvements due to AI tomorrow after accepting lots of emissions today is just a belief. There's nothing to back up it would really happen.
A bit of a rant, but since it looks like people are still trying to consider all those technologies are equivalent... I think it's good to have an explanation on what makes containers different.
Looks like a good set of tips of get more DDD practices in place without the badly understood vocabulary which usually comes with it.