Oops... security flaws ready to exploited in Wi-Fi again. And that includes WPA3.

Interesting piece covering: how a memory allocator works, why it can be slow, how to use it the best way possible and how to pick an allocator for your project.

This is a very interesting deep dive in how branch predictors work. Also comparing timing profiles between different families of CPUs.

Sounds like an interesting tool for Python projects.

Ever wondered what's hiding behind a mutex? This article goes a good job to explain this.

A good example of using the best tool for the job. Having your whole data analysis pipeline in pandas might not be what you want for performance reason. Very often there's a relational database you can leverage first.

Excellent reminder about where the limit is for the compiler to optimize things. Nowadays it's mostly about the memory accesses and then it means that the design matters a lot. Object-oriented designs being far from optimal here. Data-oriented designs fare much better but are definitely less friendly for human brains to reason about them.

Looks like the situation is still fragile for Linux phones but it's brighter than ever.

Not very scientific but gives a rough idea of which services are heavy or not in the fediverse. Matrix seems to be still dismal in that regard... I wonder if we'll see a revival of XMPP, that'd be very funny.

Nice summary of several security headers you can have to deal with for HTTP.

Interesting question, and luckily the top answer is coming from someone who put in the work and memory to do a thorough history recap. Interesting stuff.

This is a good resource explaining most of what one needs to know about Cross Origin Resource Sharing (CORS). As usual in such articles, the historical bits are particularly insightful.

Interesting take on why AI gets constantly displaced by more mundane metadata.

Interesting move, sounds like a much better path than the SSPL one.

Nice collection of effects which can be done purely using CSS. Really shows that JavaScript is often over used.

Very good piece, I agree with all the advices in there. That being said, it's often difficult to apply. This is because it requires quite a lot of self-awareness from teams and not everyone is willing to work on themselves to realize their weaknesses in the first place.

Also I'd stress one point which I don't find pushed enough in that article. Very often you want persons who might not make your team stronger now but will over time. This even works better in my experience. Hiring is a bit like gardening in a way: it's also about keeping in mind how the people joining the team will bloom in that particular context and how it'll improve the landscape.

Or why you need proper product management: it requires skills and time. Otherwise it's just botched and product gets developed in "firefighting mode" all the time. This article is a good primer on a few technics for grooming the product backlog.

Good advices and good comparison of different ways to provide feedback.

Interesting simple exploration. This seems to confirm that there's a lot of hype all around. Whatever the language, even if it is hot today it probably won't look as fun tomorrow when you'll have to maintain millions of lines of it.

Looks like an interesting tool for semantic checks on a codebase, especially on CI. Looks like it makes writing such checks easier.