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.

Clearly a new OpenSSH feature to keep an eye on. This should improved security of the server by default. That said, it needs to be a bit more in the wild before knowing how to best tune it.

This is indeed surprising behavior and specific to Windows. If you wonder why TCP connect is slow and you got IPv6 support active this might be why.

Interesting, it confirms garbage collectors can be the source of unrecoverable performance degradation in request based systems.

Of course it sounds complicated to break Google up... but that's not the point. It's about avoiding its monopolistic position, the fact that it's complicated is just another symptom.

Or why anticipating too much is merely a gamble. You can be lucky, but how often will you be? Also I agree that in such cases the performance will be impacted longer term leading to a death by thousands of paper cuts.

Retries are becoming common place to deal with transient errors. That said, they can be a problem with recovery of longer failures due to amplification. There are options on the table to solve this though.

Interesting take, those bugs are more convenient to exploit. Logic bugs are too specific to easily exploit at scale.

Need to duplicate data in Postgres? Several options are on the table.

Looks like an interesting tool for creating anonymized pre-production environments.

Compile time reflection in C++ will indeed be a big deal.

Funny short video, I guess it has also some tutorial value to know what you can do with Blender? (and no, you can't break the fourth wall with it)