In this episode of Technical Debt: Design, Risk and Beyond, hosts Maxim Silaev and Nikita Golovko break down one of the most widely documented technical-debt disasters in modern enterprise IT: the failed 2018 TSB Bank migration. More than two million customers lost access to their accounts, systems malfunctioned for weeks, and leadership was forced to answer to regulators. But behind the headlines lies a deeper lesson: technical debt exists at multiple layers: strategic, product, and architec...
All content for Technical Debt: Design, risk and beyond is the property of Maxim Silaev & Nikita Golovko and is served directly from their servers
with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
In this episode of Technical Debt: Design, Risk and Beyond, hosts Maxim Silaev and Nikita Golovko break down one of the most widely documented technical-debt disasters in modern enterprise IT: the failed 2018 TSB Bank migration. More than two million customers lost access to their accounts, systems malfunctioned for weeks, and leadership was forced to answer to regulators. But behind the headlines lies a deeper lesson: technical debt exists at multiple layers: strategic, product, and architec...
In this episode, we explore how technical debt is not just a code problem — it's a cultural one. Together, we unpack the elements of a healthy engineering culture that naturally guards against the slow decay of software systems. We start by defining what “engineering culture” really means and how it silently shapes every architectural decision, shortcut, and trade-off. From there, we dive into practical habits and team rituals that act as cultural safeguards: meaningful code reviews, shared c...
Technical Debt: Design, risk and beyond
In this episode of Technical Debt: Design, Risk and Beyond, hosts Maxim Silaev and Nikita Golovko break down one of the most widely documented technical-debt disasters in modern enterprise IT: the failed 2018 TSB Bank migration. More than two million customers lost access to their accounts, systems malfunctioned for weeks, and leadership was forced to answer to regulators. But behind the headlines lies a deeper lesson: technical debt exists at multiple layers: strategic, product, and architec...
