What's the link between the Quebec Bridge and the 737 max? Different eras. Different industries. But the same reasoning that lead to catastrophic results: move faster cheaper, even if it means lowering quality standards. In both cases, consequences were terrible: we thought sacrificing rigor would save time and/or money, but the opposite happened.

When it comes to software, stakes might not be as visible, but the same trap is there: when we aim for quick and dirty, things end up grinding to a halt. Bugs, refactoring, technical debt: what we think we saved today, we pay for it tomorrow — with interests.

What if we abandoned the false premise that we have to choose between "fast", "cheap" and "well done"? What if we finally realized that the only way to be fast is to do things right from the beginning?