Interesting trick in Java internals which is especially improving map lookups.

This is an important position paper in my opinion. The whole obsession towards the ill defined "AGI" is shadowing important problems in the research field which have to be overcome.

This move is really unsurprising... It's bound to become another channel for advertisements to try to cover the costs of running it all.

A bit long and dated for a some advice. Still it does a very good job going through all the different type of tests you'll want to find on your project and how they're structured.

Need to teach security basics to your family, friends and neighbors? Here is a nice resource to do a good job there. We often approach the task the wrong way.

A good in-depth article about pair programming. Shows well the pros and cons.

We often hear that question about the trade off between quality and cost. The question is badly framed though. If it's low quality it's requires more effort to add or change features... and so it's more expensive mid-term (not even long term).

A good reminder that reviewers have many things to keep in mind and evaluate. This is why what can be automated should be automated.

This is one of the best references I know on the topic. It's not that long, to the point and all developers should know it.

They're so misused that it's better to let them go. Indeed, we can go as far as wondering if estimating stories instead of slicing them is a good idea at all. Doesn't mean all estimates disappear of course, but at the single story resolution? You likely better invest time in slicing them better.

Or why the term "user" in "user stories" need to be seen very liberally.

Good proposals to shorten the time spent executing tests. Tighter feedback loops make everyone happy.

I have a hard time seeing browser makers truly drop third party cookies without pushing a worse replacement first... Still, it's nice to see the W3C take a stand in the matter.

Of course it helps also against DDoS attacks... tells something about the state of AI scrapers I guess.

Of course, we'd like more to go away... But that's already something.

They've been warned of this leak by GitGuardian weeks ago... and did nothing. For people manipulating such sensitive data their security practices are preposterous.

There are clearly more to know. But this is a good list already.

What is the "Whole Team" practice from XP? Well, it's fairly simple in the end... it's about collaboration really. Needs to be reminded often though.

Testing sync engines can be especially challenging. This story from Dropbox gives ideas on how to do it well.

Short and to the point. It needs repeating from time to time for some reason.