The nineteenth century saw an increasing separation between the treatment of the surface and the structure of designed objects. Mass production and a mobile market economy encouraged the production of heavily ornamented yet cheaply fabricated products. Affordable manufacture allowed the burgeoning middle class to acquire “luxury” goods fashioned after objects formerly reserved for an elite.
Put together with odd bits of the useless Clarice, a survivors’ Clarice was taking shape, all huts and hovels, festering sewers, rabbit cages. And yet, almost nothing was lost of Clarice’s former splendor; it was all there, merely arranged in a different order, no less appropriate to the inhabitants’ needs than it had been before.
The idea of overlap, ambiguity, multiplicity of aspect, and the semilattice are not less orderly than the right tree, but more so. They represent a thicker, tougher, more subtle and more complex view of structure.
Most objects which we are accustomed to call beautiful, such as a painting or a tree, are single-purpose things, in which, through long development or the impress of one will, there is an intimate, visible linkage from fine detail to total structure.
The resistant virtues of the structure that we make depend on their form; it is through their form that they are stable and not because of an awkward accumulation of materials. There is nothing more noble and elegant from an intellectual viewpoint than this; resistance through form.
Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business.
Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'.