Indeed, without deciding to put everything in the public domain, the face of the web would have been very different.

I must resist to redesign my blog I guess... In any case, this is a very nice style for content.

Looks like nice projects. After all these years I'm still amazed at what people manage to achieve in their spare time when they get together to solve a problem.

There are really many initiatives to make C and C++ safer lately. I wonder which one will see adoption and what will make its way to the standards.

Interesting approach. I did quite some of that but without really putting it together like this. It's a nice way to explain it.

Nice overview of what it takes to increase your uptime. It can get expensive quickly. This is also a good reminder that it's not only about software, it's a lot about people and administrative constraints as well.

What the title say. This is especially important for product development. This is not emphasized enough in the article I think but the "aligned autonomy" section is a crucial part of this. I very often see in teams either alignment or autonomy, it's rarer to see teams with both.

Interesting results. This gives a couple of insights in terms or adoption, perception of problems by people on C++ projects and tooling. It's definitely worth skimming through.

This is currently a real zoo. I knew about a few of them but not that many. I guess it will slowly converge toward a few major options.

Nice short post listing the main positions (and linking to corresponding articles) on the debate around technical debt. Worth mulling over all those.

Nice set of tips, I knew a few but not all of them. The discussion around CTEs is interesting.

Since I've seen this argument floating around more than once, it's nice to have a properly done rebuttal of it. This is nicely done, listing the own bias of the author, still in the end that shows the logical flaw of the argument.

Yep, disappointing indeed... I got a phone with a third party ROM and had to debug the A-GPS in there (don't ask), it's indeed reaching to this website as well. There's enough to criticize without crying wolf for nothing.

We still don't really know (actually it's super hard to have a definitive reason on this topic). This article presents more of a theory based on geometry... and this is interesting, we often don't think about this kind of things.

So much this, managing notifications and making sure not to get disturbed when we need to focus is essential in our line of work.

Good article on when to use comments or not. Also gives a few tips on how to write them properly.

Concerning moves on the ICANN side... already in the agreements around .com and now trying to make its way into .net.

Interesting experiment even though it's still early days for this kind of research and we'd need more such evaluations. They found that it produces mostly insecure code. This is not really surprising in the end, this manipulates language but has not execution model. It can be fixed only by coupling to some outside system.

If regularly see people propelled tech leads without really knowing what it means. This short post is a good summary of the skills one needs to build to fit the role.

Nice post full of good advises for new (or not so new) managers.