Hosted by Maxim Silaev & Nikita Golovko · 🇺🇸 US · EN-US · 15 episodes
Established thought leaders with verified media credentials.
We talk to experienced architects and technology leaders about the architectural choices they’ve made — the good, the bad, and the costly. From scaling systems to integrating legacy platforms, from misaligned domains to governance gaps, we discuss how architecture impacts technical debt. You’ll hear honest stories of architectural missteps, what teams learned from them, and how they built systems designed not just to work, but to last.
Maxim Silaev & Nikita Golovko hosts Technical Debt: Design, risk and beyond, a technology show with 15 episodes published.
In this episode of Technical Debt: Design, Risk, and Beyond, we look at technical debt from a place it’s rarely discussed - the CEO’s desk. My guest is David Cruz , Founder & CEO of Elmaextro , certified business coach,
In this episode of T echnical Debt: Design, Risk and Beyond , Maxim Silaev speaks with Erioluwa Asiru , CTO at CircleFunds , about what technical debt really looks like inside a fast-growing fintech operating in an emerg
In this episode of Technical Debt: Design, Risk and Beyond , Maxim Silaev is joined by Rob Broadhead , a technology leader with more than 30 years of experience across enterprise systems, startups, and consulting. Togeth
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 mi
What happens when a company’s biggest vulnerability isn’t its software, but its communication? In this episode of Technical Debt: Design, Risk and Beyond, hosts Maxim Silaev and Nikita Golovko explore the collapse of Int
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-
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 b
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 Technic
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
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 engineer
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
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 ar
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 architectu
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
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
Sponsor detection runs nightly. Check back soon.
No public pitch examples yet for this show.
Generate your own personalised pitchBased on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:
Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.
Shows with the most semantically similar episode content. Pitch one, pitch all; producers cluster.
To pitch Technical Debt: Design, risk and beyond, visit https://arch-expert.com for contact information, then craft a tight one-paragraph hook that ties your expertise to a gap in their recent technology coverage.
Technical Debt: Design, risk and beyond is hosted by Maxim Silaev & Nikita Golovko. The show is categorised under technology and has published 15 episodes.
Technical Debt: Design, risk and beyond has published 15 episodes.
Technical Debt: Design, risk and beyond regularly covers technology. It sits in the technology category.
Technical Debt: Design, risk and beyond is accessible for guests with genuine technology expertise. A personalised, episode-aware pitch will still outperform a generic one every time.
Technical Debt: Design, risk and beyond hasn't explicitly signalled guest openness in recent episodes. That doesn't rule out pitching. your hook just needs to be especially compelling and relevant to their recent content.
Episodes of Technical Debt: Design, risk and beyond average 26 minutes. a focused format where a clear narrative arc and tight preparation matter most.
Our data rates Technical Debt: Design, risk and beyond's guest bar at 80/100 (Premium tier). Established thought leaders with verified media credentials. Sign in to PitchCentric to see how your own Pod Score compares against this show.
Methodology. Booking Probability™ blends Listen Score, 30-day Virality, open-to-guests detection, and Apple ratings. Data refreshed every 60 minutes. Listen Score and Booking Probability are calculated by PitchCentric. Last enriched 7 days ago.
