Flaws, Faults, Imperfections
Merely a building
Bells
Roughness
White cloth
The aesthetic potential of flaws
Things that shine and glitter
We find it hard to be really at home with things that shine and glitter. The Westerner uses silver and steel and nickel tableware, and polishes it to a fine brilliance, but we object to the practice. On the contrary we begin to enjoy it only when the luster has worn off, when it has begun to take on a dark, smoky, patina.
A sterile sameness
Another kind of random variation involves the interaction of the craftsman’s skill and the texture of materials. The letterforms of Griffo and Colines were cut with immense care. But the letters they cut were struck by hand in copper or brass, then cast and dressed and set by hand, inked by hand with handmade ink and printed by hand in a handmade wooden press on handmade paper. Every step along with way introduced small variations planned by no one. In the world of the finely honed machine, those human-scale textures are erased. A sterile sameness supervenes.
The computer is, on the face of it, an ideal device for reviving the old luxury of random variations at the threshold of perception (quite a different thing from chaos). But conventional typesetting software and hardware focuses instead on the unsustainable ideal of absolute control – and has been hamstrung in the past by the idea of a single glyph per character. There have been several recent attempts to introduce a layer of random variation, but all have had to work against the grain of technological development.
Delight in the imperfect
An Article by David R. MacIverI think part of the difficulty in allowing ourselves to properly delight in the imperfect, comes from conflating delighting in something with wanting it to happen. This isn’t the case. You can appreciate something as it exists while acknowledging its problems. You can see that a fire is beautiful without becoming a pyromaniac, and you can appreciate the absurdity of your political situation without thinking it’s good.
Even if a delight in the imperfect causes you to want more imperfection in your life (and it should), there is no shortage of imperfection to seek out. The imperfect is not scarce, it’s abundant. If you find imperfection delightful, you will never be short of things that delight you, even if you fix any given problem. Solving problems and smoothing out imperfections doesn’t remove the source of delight, it merely opens up new vistas for it. You could give yourself over totally to delight in the imperfect and never run out of things to explore, even without creating your own.
How the light gets in
A Quote by Leonard CohenThere is a crack in everything.
That's how the light gets in.
Software that nobody wants
Finding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
The 'date scrum' anti-pattern
Date Scrum is an R&D pattern where developers are asked to estimate software project requirements upfront for the entirety of the project. After the project is green lighted and the budget is set based on the final estimates, the team then holds daily scrums to status and manage risk as they “iterate” the solution toward the release date. To some, this approach is described as doing Waterfall in sprints.
The fundamental problem with Date Scrum is that the team is de-focused from discovering the best solution. Instead they are heavily focused on delivering Something™ by the Date™. Engineers are problem solvers, and if the primary problem becomes delivering Something™ that will pass QA by the Date™, they will, with enough pressure, solve that exact problem.