Very interesting paper about the energy footprint of the latest trend in generator models. The conclusion is fairly clear: we should think twice before using them.
Very nice collection of stories from the trenches of Firefox development. Lots of lessons learned to unpack about optimizing for the right thing, tooling, telemetry and so on.
An important question for proper statistics about the content itself. Surprisingly harder to get an answer to it than one would think.
Interesting framework. I wouldn't take everything at face value, but this looks like a good source of inspiration to design your own.
A bit too archetypal for my taste but there's some truth to it. If you lean towards "explorer" (I think I do), it's hard to be also a leader. Now you could be aware of your flaws and put tools in place to compensate for them when you need lead.
New technique for SMTP smuggling... vulnerable servers then allow to spoof while still passing DMARC checks properly. Check your providers and server configuration.
Very interesting musing about undefined behaviors and language constraints. This is a bit Rust focused for obvious reasons but is also looking at what other languages have been doing.
Interesting inference engine. The design is clever with an hybrid CPU-GPU approach to limit the memory demand on the GPU and the amount of data transfers. The results are very interesting, especially surprising if the apparently very limited impact on the accuracy.
A bit of an older article I'm bumping into again. It lays out fairly well the current limits and issues with Free Software as it is defined today. I'm unconvinced it can be solved via licenses but the debate needs to happen... I feel that somehow it's too much ignored.
Interesting finding. This shows a potential issue in how identities are verified by providers.
This is a good set of advices for beginners. I especially like the ones about best practices, trying different things and why it makes sense to be conservative tech wise.
Nice state of the art view on how dynamic dispatch is implemented in several languages. Does a good way showing the trade-offs involved.
Good approach for tackling it indeed. The crux of the issue is really measuring the tech debt since it's still a fuzzy concept and we have no good metrics for it.
Here we are... We're really close to crossing into this territory where any fiction can disguise itself for reality. The problem is that we'll literally be drowning in such content. The social impacts can't be underestimated.
Interesting technique to speed up the generation of large language models.
Wonder how to implement such real-time simulations? This is a good summary of all the math involved. Also comes with code snippets and demos.
Interesting story about using unit tests by someone who thought it was a waste of time... until, they helped uncover a bug which was widespread. Also it was in an embedded context which comes with its own challenges.
This is indeed a more complex topic than it sounds. When someone complains about "technical debt" always inquire what it really means to them, what this is about, what are the symptoms.
That's a very good question. What will be left once all the hype is gone? Not all bubbles leaving something behind... we can hope this one will.
When SEO and generated content meet... this isn't pretty. The amount of good content on the web reduced in the past decade, it looks like we're happily crossing another threshold in mediocrity.