4 ms·
Same principle applies here as with any software development effort. There are some natural bottlenecks that can't be avoided/parallelized (for e.g. waiting for
by rafiki6 7y ago
Same principle applies here as with any software development effort. There are some natural bottlenecks that can't be avoided/parallelized (for e.g. waiting for a layer of asphalt to dry). Further, more people doing a thing doesn't mean it will get done faster. You have to contend with overhead of planning, context-switching and handover overhead between workers leaving/starting shifts etc. etc.
- athenot 7y agoTrue but those constraints can result in more creative engineering. Look at this timelapse of a bridge getting replaced in 43 hours. They had the new bridge built next to the orignal and "just" moved it into place—I'm using quotes because of course that is an impressive operation. https://www.youtube.com/watch?v=vz_j_BEkVCQ https://www.youtube.com/watch?v=vz_j_BEkVCQ
- thehappypm 7y agoThis does happen in the US where it's cost effective. The Tappan Zee Bridge was replaced by a new bridge built completely from scratch in parallel, then the old bridge decommissioned.
- Steltek 7y agoYou may want to check out how the Comm Ave bridge over the Pike was replaced in Boston. It was pretty quicke although not as fast 43 hours. However, we also couldn't afford to close the lower road (I-90) as above for an extended staging effort. I believe rail lines were only impacted on two weekend pushes. https://www.youtube.com/watch?v=zNiACLQtHyg https://www.youtube.com/watch?v=zNiACLQtHyg