Half a century ago, Stern discussed this attribute of an artistic object and called it apparency. While art is not limited to this single end, he felt that one of its two basic functions was "to create images which by clarity and harmony of form fulfill the need for vividly comprehensible appearance." In his mind, this was an essential first step toward the expression of inner meaning.
The personal experience of most of us will testify to this persistence of an illusory image long after its inadequacy is conceptually realized. We stare into the jungle and see only the sunlight on the green leaves, but a warning noise tells us that an animal is hidden there. The observer then learns to interpret the scene by singling out "give-away" clues and by reweighting previous signals. The camouflaged animal may now be picked up by the reflection of its eyes. Finally by repeated experience the entire pattern of perception is changed, and the observer need no longer consciously search for give-aways, or add new data to an old framework. They have achieved an image which will operate successfully in the new situation, seeming natural and right. Quite suddenly the hidden animal appears among the leaves, "as plain as day."
Everything points to the conclusion that the phrase 'the language of art' is more than a loose metaphor, that even to describe the visible world in images we need a developed system of schemata.
Craftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users.
What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless.