The advice is sound. Having more written records of such things definitely help teams. It can have a benefit in other forms (notes or todo's) if you do it just for you.

Excellent piece, looking back to history to justify why microservices are mostly a fad. Check what your needs really are and depending on them pick the right way to decompose the problem or organize your teams.

Very good primer on Conway's Law by Martin Fowler. Definitely recommended, obviously this is just a start and requires diving deeper in the topic.

Nice summary of common terms used for roles in companies.

Very good point, make sure you know how much you can take and how much you're actually carrying. We're our worst enemy for these things.

Interesting way to highlight Goodhart's Law. Indeed you can be corrupted by the very system you put in place if if it's mainly driven by metrics. As much as possible, think qualitative, not quantitative.

A very important and unfortunately underestimated factor for a sane and welcoming culture.

Interesting point of view. Indeed what might look like magic skills can simply be about having gathered more information. That thus depends on the organization.

Lots of good advices about processes and organizations. It's nicely points out that friction is not necessarily wrong... if you get something out of it.
Also neat reminder in there that code review are here to complete work which is already socialized somehow. If you can't find reviewers it's a sign of an organizational problem when the work started.