Zoning for diversity As production becomes increasingly clean and knowledge-based, as our urban economies tip dramatically to service industries, as racism and ethnic animosities ebb, and as the model of mixed use becomes more and more persuasive and visible, cities are in a position to dramatically rethink zoning as a medium for leveraging and usefully complicating difference, rather than simply isolating it. Michael Sorkin, 20 Minutes in Manhattan zoningrace
The greatest flaw in city zoning Raskin, in his essay on variety, suggested that the greatest flaw in city zoning is that it permits monotony. I think this is correct. Perhaps the next greatest flaw is that it ignores scale of use, where this is an important consideration, or confuses it with kind of use. Jane Jacobs, The Death and Life of Great American Cities zoningmonotonyscale
The air doesn't know about zoning boundaries Work uses suggest another bugaboo: reeking smokestacks and flying ash. Of course reeking smokestacks and flying ash are harmful, but it does not follow that intensive city manufacturing (most of which produces no such nasty by-products) or other work uses must be segregated from dwellings. Indeed, the notion that reek or fumes are to be combated by zoning and land-sorting classifications at all is ridiculous. The air doesn’t know about zoning boundaries. Regulations specifically aimed at the smoke or the reek itself are to the point. Jane Jacobs, The Death and Life of Great American Cities zoningregulationsseparation
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