If there's one area where people should stay clear from LLMs, it's definitely when they want to learn a topic. That's one more study showing the knowledge you retain from LLMs briefs is shallower. The friction and the struggle to get to the information is a feature, our brain needs it to remember properly.

That's an interesting approach. Early days on this one, it clearly requires further work but it seems like the proper path for math related problems.

I wonder what the whole series will give. Anyway I very much agree with this first post. Too often projects have a single product manager and that's a problem.

The findings in this paper are chilling... especially considering what fragile people are doing with those chat bots.

Didn't know about that clippy feature. This is neat, allows to precisely target some of your project rules.

Wondering what happened at Cloudflare? Here is their postmortem, this is an interesting read.
Now for Rust developers... this is a good illustration of why you should stay clear from unwrap() in production code.

Kind of ignore the security impact of the needed upgrades, but apart from this I largely agree. Most applications try to push more features in your face nowadays, unneeded notifications and all... this is frankly exhausting the users.

This is a nice little algorithm and it shows how to approach it in Python while keeping it efficient in term of operations.

If you're dealing with multithreading you should not turn to mutexes by default indeed. Consider higher level primitives and patterns first.

Struggling to understand tangent space and normal maps? This post does a good job to explain where this comes from.

I don't get why object oriented programming gets so much flack these days... It brings interesting tools and less interesting ones. Just pick and choose wisely like for any other paradigm.

Friendly reminder following the Cloudflare downtime earlier this week.

Podman is really a nice option for deploying containers nowadays.

Clearly AMD is now well above Intel in performance around AVX-512. This is somewhat unexpected.

Unsurprisingly the news ain't good on the front of social media and short form videos. Better stay clear of those.

Some of this might sound obvious I guess. Still there are interesting lesser known nuggets proposed here.

Good list of hardening options indeed. That's a lot to deal with of course, let's hope this spreads and some defaults are changed to make it easier.

This is totally misguided... Let's hope no one will succeed passing such dangerously stupid bills.

Interesting move on the Scrum definitions to move from roles to accountabilities. The article does a good job explaining it but then falls back into talking about roles somehow. Regarding the tech leads indeed they can work in Scrum teams. Scrum don't talk about them simply because Scrum don't talk about technical skills.

The type inference in C++ can indeed lead to this kind of traps. Need to be careful as usual.