Recently I saw in a program in Television in which there was new technology developed by Japanese to destruct a building in a phased manner without noise, smell or dust in the middle of a crowded city.
The news article can be found here. For readers I am pasting the main content from this site for easy reading.
The Grand Prince Hotel in Akasaka which was built in the 1980s, previously stood tall at 460 feet until the Taisei Corporation demolished the building from the inside on a floor by floor basis, reportedly losing two floors every 10 days. The innovative Taisei Ecological Reproduction System (TECOREP) is a potentially efficient approach to deconstruction in densely built cities, also designed to recycle the energy pent up in a tall building. The top floor was reinforced by engineers with steel beams, and subsequently severed but kept in place to be used as an adjustable lid which could be lowered down on the building on an external support frame.
“In this demolition scheme, the building shrinks and disappears without you noticing,” said Hideki Ichihara, manager of the Taisei Corporation. “Dust pollution is cut by more than 90 percent, keeping the environmental impact very small.”
I watched the program and was amazed by it. Such a cool idea to destruct a structure as huge as this for me was awesome.
In the next few days I didn’t think of it and one fine day during an interacting session with my colleagues at office it was conceived that the current product on which we Software Engineers were working on needs uplift in technology and architectural aspects (overhauling). Since in Japan it was destruction which was done in a phased approach, I didn’t think there was any synergy that I could think of something like this in the case of a software application/product.
I then accidentally stepped on a recent article by Martin Fowler (Genius)in here. Suddenly I could see a co-relation or rather synergy between the Japanese way of building destruction with Martin Fowler’s way of uplifting/rejuvenating an existing software application/product.
I wouldn’t want to take any content out of his article and make my own article as no one in the world can write an article in such plain English as Martin. He explains this concept in such an easy manner that a lay man could easily get crux of what he wants to say.
There are some cool references in his article which also is a definite read.
Page Visitors: 236
Latest posts by Tomcy John (see all)
- A Guide to Continuous Improvement for Architects - February 2, 2023
- Cloud-first Architecture Strategy - January 26, 2023
- Architecture Strategy and how to create One - January 24, 2023