spirit
Ordinariness
Flight of the soot sprites
The ancient fire spirit who lived in the hearth
The garden is as central to the concept of an Islamic home as the hearth is to the European home. It is interesting, then, that the hearth-fire in old traditions has a similar association with the life of the inhabitants of the house.
Commonly, the fire of the hearth was not allowed to go out. It was carefully covered with ashes each night at curfew so that a few selected embers would survive until morning. (In fact, the word "curfew" originated from the French word for cover-the-fire—couvre-feu.) Raglan comments that "the alarm and horror felt if the hearth-fire went out are out of all proportion to the inconvenience caused" by the need to relight it.
Retained as a quality
Thermal information is not differentiated in our memory; rather it is retained as a quality, or underlying tone, associated with the whole experience of the place. It contributes to our sense of the particular personality, or spirit, that we identify with that place. In remembering the spirit of a place, we can anticipate that if we return, we will have the same sense of comfort or relaxation as before.
Roaming and capricious
Now I sometimes wonder whether the current of utility has not become too strong and whether there would be sufficient opportunity for a full life if the world were emptied of some of the useless things that give it spiritual significance; in other words, whether our conception of what is useful may not have become too narrow to be adequate to the roaming and capricious possibilities of the human spirit.
My Neighbor Totoro
A Film by Hayao MiyazakiSpirited Away
A Film by Hayao MiyazakiAvatar: The Last Airbender
A SeriesThe Legend of Korra
A Series
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.