imperfections
The monotonous perfection
The mathematical physicist must simplify in order to get a manageable model, and although his concepts are of great beauty, they are austere in the extreme, and the more complicated crystal patterns observed by the metallurgist or geologist, being based on partly imperfect reality, often have a richer aesthetic content. Those who are concerned with structure on a super atomic scale find that there is more significance and interest in the imperfections in crystals than in the monotonous perfection of the crystal lattice itself.
The aesthetic potential of flaws
The archaeological quality of this section of exposed wall provides an example of the aesthetic potential of that which is flawed or broken.
A Painted Karatsu as Food for Thought
Recently there is a tendency to pursue distortion in art, but in the case of this jar, natural deformation has raised distortion to the level of spontaneous beauty.
The Japanese Perspective
An Essay from The Beauty of Everyday Things by Yanagi SōetsuGenerally speaking, the Western perception of art has its roots in Greece. For a long time its goal was perfection, which is particularly noticeable in Greek sculpture. This was in keeping with Western scientific thinking; there are no painters like Andrea Mantegna in the East. I am tempted to call such art ‘the art of even numbers’.
In contrast to this, what the Japanese eye sought was the beauty of imperfection, which I would call ‘the art of odd numbers’. No other country has pursued the art of imperfection as eagerly as Japan.
Is perfection boring?
An Article by Ralph AmmerWe love to see the process, not just the result. The imperfections in your work can be beautiful if they show your struggle for perfection, not a lack of care.
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.