The Apollo | Euro Cut | Ep 208

Managing Technical Debt During Periods of Rapid Growth

1:33:30 – 1:36:453:15 long

The speakers analyze the trade-offs between shipping new capabilities quickly and refactoring underlying legacy systems.

The discussion transitions into the challenges of maintaining code health while scaling up engineering operations. The host asks how organizations can systematically address technical debt without completely halting the delivery of new features to market.

The guest states at 4:10 that technical debt is an inevitable consequence of rapid growth rather than a simple management failure. They argue that treating all code debt as equally urgent leads to paralysis, suggesting instead that teams categorize debt based on its direct impact on system performance and developer velocity.

At 5:15, the host points out that infrastructure bottlenecks frequently emerge when software usage scales faster than anticipated. In response, the guest advocates for allocating a fixed percentage of every development cycle specifically to refactoring and infrastructure modernization.

By 6:15, the guest emphasizes that transparent communication between product managers and engineering leads is essential. They conclude that framing refactoring tasks in terms of risk reduction makes it easier to secure organizational buy-in for ongoing system maintenance.