

Building For The Future
Sep 15, 2025
Jon Sabados, a seasoned staff software engineer at The New York Times, shares insights on building sustainable software systems that can evolve over time. He discusses the importance of long-term planning to avoid technical debt and the delicate balance between speed, cost, and quality in development. The conversation delves into the challenges engineers face, the journey from legacy systems to modern solutions, and even a skeptical take on AI's future role. Get ready to rethink your approach to software development!
AI Snips
Chapters
Transcript
Episode notes
Future-Ready Work Protects Velocity
- Building for the future preserves delivery velocity when priorities shift.
- Without it, ad hoc firefighting creates tangled systems that slow development.
Make Trade-Offs With Stakeholders
- Balance speed, quality, and cost with product and engineering stakeholders.
- Revisit decisions continually as new facts and timelines emerge.
Begin With Problem Discovery
- Start discovery by understanding the user's actual problem, not requested UI changes.
- Ship a minimal, usable solution early and learn from real feedback.