251. Different Chairs Problem People are different sizes; they sit in different ways. And yet there is a tendency in modern times to make all chairs alike. Solution Never furnish any place with chairs that are identically the same. Choose a variety of different chairs, some big, some small, some softer than others, some rockers, some very old, some new, with arms, without arms, some wicker, some wood, some cloth. Christopher Alexander, Murray Silverstein & Sara Ishikawa, A Pattern Language Drawing pictures of citiesAn index of the shifting patterns furniture
An index of the shifting patterns "Because this is a garden where things can be left out at night without being stolen, we're going to 'furnish' the garden with French café chairs that won't be secured in the ground, so people can move them to wherever they want to sit...It's like with the chairs being totally casual and relaxed and comfortable. They set a tone. There's things that you have to do to get the right feel, where it's all already there, but then, you know, 'Bing!' – there's a moment of recognition." The patterning of chairs pulled together in different ways by successive waves of visitors over the course of the day becomes an index of the shifting patterns of people that sit in a variety of arrangements to facilitate conversations and other intersubjective alignments, or simply to allow for a moment of private contemplation free from contact with others. Matthew Simms, Robert Irwin: A Conditional Art 251. Different Chairs furniture
From the desk of A Blog by Kate Donnelly fromyourdesks.com A site dedicated solely to canvas of the Desk. A Desk is where we work. Symbolic. Physical. Present. A second and third home. A Desk is a platform. A hearth. Roots are planted. It’s a place, a sanctuary, where hours upon hours pass. From the desk of: Austin Kleon workfurniture
Figma's Engineering Values: Craftsmanship An Article www.figma.com 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. craftsoftwarequality