30-story building built in 15 days! Construction time lapse of J57, Changsha, China.
AI+R1 HN recommenders · 2012–2015
6.6M views · demo · dated · Uploaded 2012-01-07
Time-lapse of Broad Group erecting a 30-story prefabricated hotel (J57) in Changsha, China in about 15 days. The description touts modular construction's precision, speed and low waste.
Shared as a striking example of what prefab modular construction can achieve in speed.
18:14Stroads are Ugly, Expensive, and Dangerous (and they're everywhere) [ST05]
Not Just Bikes
11:39The Ingenious Design of the Aluminum Beverage Can
engineerguy
1:07:51Shenzhen: The Silicon Valley of Hardware (Full Documentary) | Future Cities | WIRED
WIRED Investigations
30:33Origins of Precision
Machine Thinking
29:361. How Buildings Learn - Stewart Brand - 1 of 6 - “Flow”
Stewart Brand
16:48What Really Happened During the Texas Power Grid Outage?
Practical Engineering
37:50The Art of Making a Nixie Tube
Dalibor Farný
48:53I Tried To Make Something In America (The Smarter Scrubber Experiment) - Smarter Every Day 308
SmarterEveryDay
3 comments from Hacker News
Actually not BS, see the Broad Group's web site and their timelapse of the 'demo' project [1]. They don't count the time to put in the foundation and drive the pilings, just the erection part. That part consists entirely of lifting pre-fabricated sections in place, connecting pipes and wires, welding to the rest of the building and moving on to the next one. [1] [VIDEO]
Something like this, where they put up a 30-story building in 15 days in China. Super impressive timelapse: [VIDEO]
This format is painful to read, so I'm copying the content here. This is a series of tweets by [LINK] -- If you are using software to go after a legacy physical vertical, we are most excited if you do it "full stack" [0]. With @counsyl, we found that one cannot live by bioinformatics alone. So built a full clinical lab + software + national salesforce. Here is a video of our robotic genome factory: Also: insurance coverage, clearances, clinical integration... [1] The reason to do full stack is that it's hard to replace just one layer of an outdated legacy stack. CAC & integration costs can kill. For example, consider "restaurant powered by technology" vs "tech for restaurants". With code, reinvent industry and make better margins. You cannot automate something till you've done it manually many times. You cannot abstract an API till you've seen many specific examples. Need to build a site of the scale of [LINK] - and encounter all the problems - before you could do [LINK] . Reinventing agriculture? Build new kind of farm, w/ solar panels & self-driving tractors. Control all factors, show that code cuts costs. More examples of full stack startups.. Education: [2], Autos: [3], Hospitality: [4] By doing it end-to-end, you see things. First, sometimes a good reason beyond tradition (eg regulatory, logistical) for legacy practices. Second, your control of adjacent layers may eliminate the initial problem you were trying to solve. Analogous to: [5] Third, solving whole problem build