Blessed by the four elements The Indian stone temple also included, in its architectural form, the means for being blessed by the four elements—earth, wind, water, fire. Before entering the temple gates, one removed one's shoes to touch and be blessed by the earth. Then upon passing through the temple gateway, one is blessed by the air with a gust of wind. A blessing by water is obtained by bathing in the temple tank, or at least descending its steps to touch the water. Finally, on entering the cool interior of the sanctuary, the worshipper is given a mark on the forehead with ashes taken from a sacred flame by an attendant priest. Even this blessing by fire has a slight cooling sensation to it. Perhaps it is only coincidental that each of these four blessings is associated with a cooling sensation; and yet, the use of forms and materials that inevitably create coolness is quite remarkable. Lisa Heschong, Thermal Delight in Architecture Avatar: The Last AirbenderThe Legend of KorraA hierarchical system of sense elements
A hierarchical system of sense During the Renaissance, the five senses were understood to form a hierarchical system from the highest sense of vision down to touch. Vision was correlated to fire and light, hearing to air, smell to vapour, taste to water, and touch to earth. Juhani Pallasmaa, The Eyes of the Skin: Architecture and the Senses Avatar: The Last AirbenderPrometheusBlessed by the four elements fireelementssenses
Avatar: The Last Airbender A Series The Legend of KorraBlessed by the four elementsA hierarchical system of sense spiritelements
The Legend of Korra A Series If you look for the lightWhen we hit our lowest point Avatar: The Last AirbenderBlessed by the four elements spiritelements
Why we stopped breaking down stories into tasks An Article by Adam Silver adamsilver.io The Scrum process says to break down stories into tasks to make estimation easier, encourage collaboration and to be able to show more granular progress during a sprint. But after a few sprints, we decided to do the next sprint without creating tasks. As a result we drastically increased our velocity and never went back. Here I'll jot down some of the reasons we decided to do this: Breaking down stories into tasks is time consuming The tasks we came up with invariably would change as we worked on the stories Tasks are repetitive Tasks were often carried out in parallel Our estimates didn't improve It decluttered our task board It encouraged collaboration throughout the sprint While we started our process by following Scrum to the letter, we soon realised that breaking down stories into tasks was something that wasn’t worthwhile for us. In the end we realised that it was overplanning and poor use of our time. In the end we used that time to get on with the work and deliver at a significantly faster pace. Why We Don't Do Daily Stand-Ups at Supercede agile