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
Why Software is Slow and Shitty
Roman empire military
Rome military diagram.
Most company structures are based on the Roman empire military. CEO Caesar says he wants something, and the lieutenant managers below him on the org chart break it down into smaller tasks for the soldiers to accomplish.
On a development team, programmers are the soldiers of these shitty new armies. They open their Jira issues and add whatever feature it says to add, or fix what it says to fix. If I can save time by adding another dependency, or skip a meeting by implementing a mockup exactly as designed, why should I care?
Building is never a straight line
You might think that Mario 64 was built with tickets and sprints, but, according to interviews, there was no master plan, only the principles that the game should feel good and be fun. They started with just Mario in a small room, and tuned his animations and physics until he felt nice and responsive. After that, the levels were also created as they went, with the designers, developers, and director going back and forth using sketches and prototypes.
Building like this is never a straight line. Ideas and code get left on the cutting room floor because part of innovation is questioning whether what you made should exist. The process is cyclical and iterative, looking something like this.
Conversations, not commandments
Good software comes from a vision, combined with conversations not commandments. In a craft-focused environment, care for efficiency, simplicity, and details really do matter. I didn’t leave my last job just because I wanted to make something new. I left because I wanted to make it in a way I could be proud of.