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
Recognizing Constraints An Article by Jeremy Wagner css-tricks.com Super Nintendo games were the flavor of the decade when I was younger, and there’s no better example of building incredible things within comparably meager constraints. Developers on SNES titles were limited to, among other things: 16-bit color. 8 channel stereo output. Cartridges with storage capacities measured in megabits, not megabytes. Limited 3D rendering capabilities on select titles which embedded a special chip in the cartridge. Despite these constraints, game developers cranked out incredible and memorable titles that will endure beyond our lifetimes. Yet, the constraints SNES developers faced were static. You had a single platform with a single set of capabilities. If you could stay within those capabilities and maximize their potential, your game could be played—and adored—by anyone with an SNES console. PC games, on the other hand, had to be developed within a more flexible set of constraints. I remember one of my first PC games had its range of system requirements displayed on the side of the box: Have at least a 386 processor—but Pentium is preferred. Ad Lib or PC speaker supported—but Sound Blaster is best. Show up to the party with at least 4 megabytes of RAM—but more is better. constraints