Contrast & Differences
Their opposites close at hand
We should note that all of these places of thermal extremes (Finnish saunas, Japanese hot baths, American beaches and mountains) have their opposites close at hand. There are possibly two reasons for having the extremes right next to each other.
The first is physiological: the availability of extremes ensures that we can move from one to the other to maintain a thermal balance.
The second might be termed aesthetic: the experience of each extreme is made more acute by contrast to the other.
This is history
It is easy to see how rapidly diversity is developed by the aggregation of the simplest local choices of direction. This is history.
Contrast
Works of art which have great life often have intense contrast within: rough/smooth, solid/void, loud/silent, empty/full. It is the difference between opposites which gives birth to something. Contrast is what often gives other principles their degree of life – the intensity of the boundary, the markedness of the alternating repetition.
Contrast strengthens centers by making each a deeper entity of itself, and thereby giving deeper meaning to both. It is, at its simplest, what allows us to differentiate. But meaningless contrast remains meaningless. It is only when centers are actively, mutually, and meaningfully composed that it acts to deepen the whole.
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.