Technical Debt: Design, risk and beyond

https://is1-ssl.mzstatic.com/image/thumb/Podcasts221/v4/96/95/9d/96959d92-ba82-f9ec-0152-9df7b7da141c/mza_13769191677889806598.jpg/600x600bb.jpg

Maxim Silaev & Nikita Golovko

10 episodes

3 weeks ago

Secure Boot was designed to solve one of the most fundamental security problems in computing: how to ensure that only trusted software starts your machine. But like any architectural decision, it came with its own trade-offs, and its own technical debt. In this episode of Technical Debt: Design, Risk and Beyond, Maxim Silaev and Nikita Golovko explore Secure Boot as a case study in how solving one kind of debt often creates another. Maxim explains how the pre-Secure Boot world fragmented BIOS...

Technology

RSS

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.

Technology

Episodes (10/10)

Technical Debt: Design, risk and beyond

Secure boot: debt, trust, and the future of firmware security

3 weeks ago

14 minutes

Technical Debt: Design, risk and beyond

Technical debt beyond technology with Simon Copsey

Technical debt is not just about code! it is the visible symptom of deeper organisational issues. When companies try to move faster than their systems, teams, or leadership structures allow, debt shows up in technology but originates elsewhere. In this episode of Technical Debt: Design, Risk, and Beyond, we will talk with Simon Copsey, a management and technology leader who writes and consults on how technical debt reflects strategy, culture, and communication. Simon shares why debt is ...

1 month ago

27 minutes

Technical Debt: Design, risk and beyond

Technical debt in frontend with Christian Joecker

Frontend moves fast — but with every new framework, testing shortcut, or design compromise, teams risk piling up technical debt that quickly becomes visible to users and costly to the business. In this episode of Technical Debt: Design, Risk, and Beyond, we talk with Christian Joecker, a web developer and UX designer with over 10 years of experience helping companies like BMW, Volkswagen, United Airlines, and the Fraunhofer Institute build and scale digital products. Christian shares his pers...

1 month ago

23 minutes

Technical Debt: Design, risk and beyond

What do we mean by Architecture?

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...

1 month ago

20 minutes

Technical Debt: Design, risk and beyond

Can AI help identify hidden technical debt better than humans?

In this episode of Technical Debt: Design, Risk and Beyond, hosts Maxim Silaev and Nikita Golovko explore whether artificial intelligence can really spot technical debt more effectively than human architects and engineers. Drawing on real-world projects: from investor due diligence to scaling SaaS platforms, they share stories of how AI has surfaced invisible hotspots, misread healthy churn as risk, and mapped sprawling dependencies. Together, they examine three critical signals of hidden deb...

2 months ago

30 minutes

Technical Debt: Design, risk and beyond

What does it really mean to pay off technical debt?

We often talk about “paying off technical debt” as if it were a one-time event, but is that even possible? In this episode, Maxim Silaev and Nikita Golovko dive deep into what it truly means to address technical debt and why the language of "paying off" can be misleading. Through personal stories, hard lessons, and client case studies, they will examine when refactoring creates real value, and when it is just polishing code, and why debt reduction must be tied to business outcomes. They discu...

2 months ago

13 minutes

Technical Debt: Design, risk and beyond

Legacy is not a four-letter word: rethinking old codebases

Legacy doesn’t have to mean “bad.” In this episode of Technical Debt: Design, Risk and Beyond, hosts Maxim Silaev and Nikita Golovko discuss and challenge the myths around legacy code. They explore when legacy systems are a liability, when they’re a quiet strength, and why fear often drives decisions more than facts. Drawing from personal stories and consulting experiences, they discuss real cases where legacy code either supported growth for years or quietly undermined business stability. Yo...

2 months ago

19 minutes

Technical Debt: Design, risk and beyond

The hidden cost of scaling teams and how architecture can help

As engineering teams grow, many organizations expect velocity to increase, but often the opposite happens. In this episode, we will explore the invisible costs of scaling headcount without evolving your system architecture. From onboarding delays to tangled communication paths and team overlap, we break down why more people often leads to less effective delivery. We dive into the architectural principles that help teams scale safely: service boundaries, team ownership models, platform thinkin...

3 months ago

20 minutes

Technical Debt: Design, risk and beyond

How product strategy silently shapes your architecture, and what architects can do about it

In this episode, we explore how product strategy - even when not explicitly technical - has a profound and in most times invisible impact on software architecture. From market segmentation to feature prioritisation, many product decisions quietly affect long-term architectural consequences. We unpack how phrases like "just support one more use case" or "we might add multi-tenancy later" seem innocent, but translate directly into complexity, coupling, and irreversible system shape. When archit...

3 months ago

34 minutes

Technical Debt: Design, risk and beyond

Engineering Culture that Prevents Technical Debt

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...

4 months ago

34 minutes