It is absolutely funny that he's talking about alignment, and then you see the chevron in the "better" example :) But, kidding aside, it's a mechanistic view p

It is absolutely funny that he's talking about alignment, and then you see the chevron in the "better" example :) But, kidding aside, it's a mechanistic view patterned on avoiding egregious missteps. It's rules for creating not-bad-looking user interfaces. And... I take that. It's better than a lot of what's built. But I encourage every developer to ask "why" when looking at these rules, or when looking at components in a component library. It's a valuable exploration. It will also teach you the most important thing - and understanding when you can break the rules. Because without an occasionally broken rule, the design will be lifeless and flat.