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...
Everyone has their own definition of "architecture". For some, it is diagrams. For others, it is documentation, a set of rules, or technical excellence. Some see it as task-setting, others as an evolving discipline. But what does IT architecture really mean in practice? In this episode of Technical Debt: Design, Risk and Beyond, hosts Maxim Silaev and Nikita Golovko unpack the many faces of architecture. Drawing on real-world stories, they explore how architecture is more than static rules: i...
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...
