The wonderful thing about living in a world of our own creation is that we get to choose what kind of world it's going to be—at least in principle. But the promise is meaningful only if a broad enough "we" can be engaged in the process. At present, mechanisms and democratic institutions for making collective decisions about the deployment of technology are hopelessly cumbersome. How can anyone make a sensible choice without being able to weigh one alternative against another?
On the Situations and Names of the Winds is the title of a fragment of a pseudo-Aristotelian treatise, most likely written by a later author of the Peripatetic school. The two-page work identifies and briefly describes the names not just of the four anemoi, but gives a wind-name to each of the twelve points of the so-called “wind-rose”, slightly less poetically the “compass rose”, which is the figure seen on classical nautical charts and maps that shows the cardinal points as well as points intermediate.
...In both agricultural and maritime settings, the names of the winds were at once practical and phenomenologically basic: to step outside and to feel them was to know how things were in the most basic sense, to “know which way the wind is blowing”, as we still vestigially say, and to find the language to speak of it.
...If I were ever permitted to teach a course on the philosophy of wind, I would begin with the questions: How did the winds lose their names? And what does it mean for us to live in a world of nameless winds? I step outside and I feel a gust. “That’s wind,” I think to myself, and I have nothing more to add beyond that. I don’t know the winds.
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.