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 debtHow the constant wave of frameworks creates long-term risksThe role of testing and documentation in avoiding costly mistakesLessons from integrating new features into legacy stacksThe one piece of advice he’d give his younger self about handling technical debt📍 Connect with Christian:Website: https://jocker.devLinkedIn: 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.Send us a textReach us @ LinkedIn: https://www.linkedin.com/in/maxim-silaevhttps://www.linkedin.com/in/dr-nikita-golovko

Ver todos los episodios