50 Shades of Legacy

on YouTube ↗21m

" summary

Company is a used‑car marketplace (heycar). Claim: many “new” systems become legacy fast — example: a Swift microservice + Kafka pushed to production generates bad data and requires a manual repair script run every few days instead of a fix. Historical surprise: a 2010 mobile app chosen for cross‑compilation ran on Java without generics cross‑compile against Symbian and made sense then. Prescriptions: use ADRs and refactoring/testing books, isolate dependencies, experiment before committing.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 6:48The Ai Winter
3. 9:16Coffeescript
4. 16:14Pre Legacy

" related talks

• 48mLegacy, for lack of a better word, is goodUberto Barbini · Voxxed Days Bucharest 2018
• 54mThe Future of the Past – Legacy Will Stay With UsCarola Lilienthal · iSAQB Software Architecture Gathering – Digital 2021
• 47mLegacy Software: Really a Problem?Eberhard Wolff · Software Architecture Gathering – Digital 2023
• 14mDo Legacy Systems dream of Modernization?Katerina Andreadou · Voxxed Days Thessaloniki 2025
• 49mWhat Does a Legacy System Teach Us?Jakub Pilimon · 4Developers 2022 Online
• 41mLegacy, for lack of a better word, is goodUberto Barbini · JDD 2017
• 43mPatterns of Legacy DisplacementRob Horn, Ian Cartwright · GOTO Copenhagen 2022
• 22mThe Future of LegacyZeev Avidan · Apidays Live Hong Kong 2020