This is a discussion about refactoring vs rebuilding in mobile app development, particularly in scaling teams. The panel discusses why companies like Uber decide to rewrite their apps instead of refactoring the existing codebase, and how they balance delivering new features with preparing for scale. They share their experiences with adopting new technologies, handling legacy code, and removing old codebases from the main codebase. The discussion highlights the importance of considering the team's trustworthiness, risk, and upside/downside when deciding on a course of action.