In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub dive deep into the engineering crossroads between Better Architecture Driven Development (BADD) and Feature Driven Development (FaDD).
They unpack the eternal question faced by every CTO and engineering leader: Should we refactor now for a better tomorrow, or build features today and clean up as we go?
Drawing from decades of leadership experience, Scott and Brad share stories of modernization projects that went right—and wrong. They explore how teams can avoid “second system syndrome,” how to build alignment around what better architecture actually means, and why cultural discipline matters more than technical purity.
Along the way, they reveal:
Why “refactor everything first” often fails—and how to prevent half-finished modernizations.
The “While You’re At It” risk: scope creep disguised as progress.
How executive challenges can sharpen, not derail, technical strategy.
The hybrid middle ground—“Bad with Fad”—that blends architectural improvement with feature momentum.
Why the fastest way out of a technical hole is to stop digging deeper.
Listen in for a thoughtful, funny, and practical debate on what it really takes to evolve complex systems—without breaking the business.
Resources:
#TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCtos #Podcast #Ctos #CtoPodcast #Technology #Engineering #SoftwareDevelopment #TechLeadership #EngineeringLeadership #SoftwareArchitecture #Refactoring #TechnicalDebt #LegacyModernization #AgileDevelopment #FeatureDrivenDevelopment #BetterArchitectureDrivenDevelopment
