Rebooting the Bay Bridge: a classic rewrite story

This post was written with Mathew Spolin and published in VentureBeat. From the smallest startup to the largest multi-national company, the ground-up software rewrite is the unicorn of organizations. At some point, a software system needs to be rewritten from scratch, usually for one or more of three reasons: Architectural flaws inherent from the onset. External market conditions that the software can not meet. Too much deferred maintenance such that the software is unstable and unchangeable. Software is sometimes hard to understand as it is abstract. However, we have the ultimate physical, real-life rewrite on our doorstep here in San Francisco: the rebuild of the eastern span of the Bay Bridge. Architectural Flaws The eastern span of the Bay Bridge, first opened in 1936, had a significant architectural flaw in that it could not survive a high-magnitude earthquake. The magnitude 7 Loma Prieta earthquake in 1989 caused a 76- by 50-foot section of the upper deck to ...