Yah you get this inner platform effect where designers start unwittingly creating their own version of css using Figma and it gets really bespoke really fast.
I was making a new brand file in Figma and was about to define all the variables and aliases, paths, all that. Took one look at it and just made the 8 colors I needed and went on with the design.
TLDR: practice. If you have sufficient natural talent xor will, you will eventually go past the canon of available material and begin to transcribe your own. Then there are those who move to creation, either immediately or somewhere in the path.
Feels sloppy (is sloppy) but I think the idea is to prioritize OS unification for hardware reasons, and UX across product suite — devices can share data, apps, screens, everything.
I wonder if tube harmonics modeled by solid state settings has shaped music. Of course it has; music from that era is instrument-oriented.
The discovery of feedback tones and the resulting incorporation in the musical experience — a three hour warm bank of tubes turned up to the limit with a maxxed out savant unlocking new realms of sound.
Isn't it more of a style decision where if your team rebases, and practices clean code discipline, and excellence is a habit rather than an enforcement — the signals visibly emit in `status`.
Most committers don't really understand remotes, much less rebasing.
The second half of the post essentially describes low/high context social dynamics.
Outside of linguistucs, I've seen it applied as a concept of social group inclusion and mobility. Eg. America is a low context society — if you mess up you can move across town. Other cultures that are high context, your family will be shunned for generations with no hope of success.
I can do things that were far beyond my reach — suddenly. Almost all at once.
"Now you can discover you suck at marketing and business" :D