What do we mean by consistency? I know some people are going to say: "Hey! That's Dan Flavin's act. Why in the hell is Irwin doing a Dan Flavin? Why is he suddenly so inconsistent – fluorescent one day and Cor-Ten the next?" The key to all of this is that we have to examples what we mean by consistency. And here the critical question is: "what do we use to measure consistency with?" If you measure consistency in terms of material, or gesture, then I will be found inconsistent. But, in all of the recent pieces and proposals, if you go to the actual site and look at it, you will find that the solution is absolutely consistent on the grounds within which it responds to its environment. This in turn is consistent with my development of the implications implicit in non-object art. Robert Irwin, Robert Irwin: A Conditional Art consistency
What's suitable for each unique condition What of machines and prefabrication? How do they compare? Well, the machine has its limits. We, using handcrafted methods, do things that machines cannot do. Of course, it's not fast like a machine. And in complicated areas like here, things wouldn't go the same using a machine as it would by hand. We use numerous variations of all these connecting and splicing joints. Using a machine, [the wood joints] can all be made uniform, but really, we need to consider whether that's a good thing. It's better to make each mechanism and joint by considering what's suitable for each unique condition. Akinori Abo, Kigumi House Chopped and disfigured contextmachinesconsistency
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