Technical Debt: Design, risk and beyond
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.
Technical Debt: Design, risk and beyond
Technical debt in frontend with Christian Joecker
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
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 perspective on:
- Why frontend debt is different from backend or infrastructure debt
- How the constant wave of frameworks creates long-term risks
- The role of testing and documentation in avoiding costly mistakes
- Lessons from integrating new features into legacy stacks
- The one piece of advice he’d give his younger self about handling technical debt
📍 Connect with Christian:
- Website: https://jocker.dev
- LinkedIn: https://www.linkedin.com/in/christianjoecker
🎧 Tune in for practical stories and insights into frontend debt — why it’s visible, why it matters, and how to manage it before it manages you.
Reach us @ LinkedIn:
https://www.linkedin.com/in/maxim-silaev
https://www.linkedin.com/in/dr-nikita-golovko
