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.