Member-only story
The Two Rules of Software Architecture
A Story of Choices and Consequences
It was the summer of 1940, and Washington State was buzzing with excitement. The brand-new Tacoma Narrows Bridge had just opened — an engineering feat that promised to connect communities and fuel economic growth. People marveled at its sleek design, but something about it felt…off.
The bridge didn’t just stand — it danced. Not just a small sway, but big, rolling waves that made it seem almost alive. Locals playfully nicknamed it “Galloping Gertie.” At first, the movement was entertaining. People would drive across just to experience the bounce. But soon, what seemed like a quirky feature became a terrifying flaw. The engineers had prioritized cost and aesthetics over aerodynamics.
Then came November 7th. A strong but not unusual wind funneled through the Narrows, and Gertie began moving more violently than ever. The steel cables creaked under pressure, the road twisted, and then — snap. Within minutes, the bridge twisted, broke apart, and crashed into the water. It was a dramatic failure and a clear lesson that every decision — no matter how logical — comes with consequences.
This wasn’t about bad engineering. It was about trade-offs that weren’t fully understood. And in the world of software architecture, we make the same kinds of trade-offs…
