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.

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.

There are many more useful codes than are generally used. We shouldn't shy away from using them when it makes sense, it also means the client side must be ready for them. Very often client code makes wrong assumptions on the possible codes.

Nice exploration of false sharing on performances in several hardware scenarii. A couple of surprises along the way.

OK definitely surprising research. Some of the results are interesting. Clearly it shows a high level of socializing with those birds.

Interesting train of thoughts. Indeed we should keep in mind that large scale software is almost always a complex adaptative system, even more so if we don't forget the people developing it and not just focusing on the code. This can give us guidelines on how to organize the development.

Also does a good recap about what a complex system is and how it behaves. Definitely worth a read at least for this.

Definitely complicated to identify and resolve paths on this platform. I had to deal with it from time to time and this can definitely turn into a pain in the neck.

Are we surprised? Not at all... this is an ethical problem, this is a legal risk. The alternatives will hopefully know better.

This is really a huge update. Brings in lots of features which were clearly missing.