A little refresher about std::ref and std::cref. They come in handy sometimes, but also if you don't realize you need them you'll generate more copies than necessary.

Since they unfortunately turned on private attribution by default (why? Mozilla, why?). Here is an easy automated way to turn it off.

This is indeed a nice way to approach technical interviews. Unfortunately it requires quite some effort to setup and maintain. You also have to find the right bugs to put in the interview and this is a rarity.

With all those bots and scripts crawling the Web, some of the semantic web vision got silently implemented.

It's good to see major institutions like this get out of contracts with scientific publishing companies. Those unfortunately became mostly parasitic. Open access should be the norm for research.

It's better than no feedback. It's a bit lazy and far from perfect though.

Looks like there's another contender for package management for Python. This is sooo fragmented now... this one is compelling though.

There are many ways to create a memory leak in Javascript. Here is a good list of the things to pay attention to.

Looks like a nice tool to monitor your network.

Scary thread... developers should know better than do this and ship it on devices around the world. Their data is now anyone for the taking and users' privacy can't be ensured.

Be sure to pick the right behavior model when you make a benchmark. Otherwise you might just measure the wrong thing.

Interesting musing. The predictability in tone doesn't make for very funny content indeed. Also as a side-effect this might help people remember that Markov chain are a thing and much less expensive.

This is a good point. The DRY principle has value but the trick is finding the right time to apply it.

Very nice interview. This is an interesting reflection on the past 20+ years of Agile Software Development.

Interesting series about the rise of the javascript frontend framework, the bad practices which came with them and the very real impacts on the users. There are indeed better ways.

Nice way to keep in check how and why behavior changes as the requests from various stakeholders come in.

Looks like an interesting resource to learn about IPv6.

Interesting initiative. I'm looking forward to the results of this first pilot.

I wish more product companies would pick this license. Going for AGPL with a support and/or double license offering is a strong model in my opinion.

A new HTML attribute to keep an eye on. I can expect people to abuse it with hard to debug problems in the frontend if you don't know it is there.