|
|
|
|
|
by majormajor
1260 days ago
|
|
One of the most interesting things to me here re: the common question "why can't we build quickly anymore": "They didn’t have design loopbacks because they had extremely experienced builders. The builders knew what they were doing. They had been building skyscrapers for between 30 and 40 years and they understood what they had to pay attention to and what was possible and what had to be designed in what order to eliminate the loopback. Now, all the computers in the world: they’re not going to substitute for deep experience. I propose that if they didn’t know what they were doing there’s no way: they would not have had the chance to hit that kind of number." How many cities out there today have as many builders building skyscrapers at the same pace as they were then? Is there a way to get that speed back without the same sort of practice? --- The workflow/independent stuff is also very interesting, but similar to the above question, it's tough to draw exact parallels to software. We've all seen big waterfall projects fail, and the "design floors on the fly independently" aspect has a lot of similarities with rapid iteration, etc, but software is somewhat different in that the labor and the design are the same - there isn't a "steel team" and a "concrete team" etc that can work completely independently, I don't think. "Create the schedule and then figure out the project" is probably a super useful takeaway, though. |
|