While I enjoy this kind of resource, I miss some explanation about why they recommend doing things that way.
When championing good practices like these within a team, they are often somehow challenged, and "do it because I say so" is a weak answer.
Also, not understanding why these are good practices is a good way to end up doing cargo cult architecture.
Edit:
> Some of the choices I’ve listed so far may seem arbitrary, and they are! You and your team should make aesthetic changes if you want to, but I urge you to define them on a system level. If you can’t agree on something that is subjective, I recommend that you just do what I said, because it doesn’t matter and this way of doing things is already written down.
When championing good practices like these within a team, they are often somehow challenged, and "do it because I say so" is a weak answer.
Also, not understanding why these are good practices is a good way to end up doing cargo cult architecture.
Edit:
> Some of the choices I’ve listed so far may seem arbitrary, and they are! You and your team should make aesthetic changes if you want to, but I urge you to define them on a system level. If you can’t agree on something that is subjective, I recommend that you just do what I said, because it doesn’t matter and this way of doing things is already written down.
That's a very good point.