Can't the author's view be fitted into an interative process though? Like, the design version of avoiding premature abstraction. He mentions "product teams" m

Can't the author's view be fitted into an interative process though? Like, the design version of avoiding premature abstraction. He mentions "product teams" moving faster than the design system, which creates pressure to extend the design system. This can lead to flawed implementation of the design system. So maybe the product team should go with some band-aid during development if needed, and explicitly pass the requirements to the design system team, who can then refine and extract reusable components. Add of course, steady communication between people implementing features and people implementing design components should accompany this process. I am not sure if that's what TFA means, because I haven't read the whole thing. But I think design systems should be polished, simple, and provide a rock-solid API, and I think that the way to achieve this really might require patience. It's not even needed to have these tasks be distributed among strictly separate teams to follow this line of thought, right? Could be the guiding principle even of one single developer.