In this episode, Matt and Liam dive into the topic of app modernisation. Should you keep your software modern, or is it an inevitable slide into obsolescence? How do you balance tech debt, business priorities, and ever-changing frameworks?
They discuss:
✔️ The trade-offs between technical debt and modernisation
✔️ Why some applications are designed to be replaced rather than maintained
✔️ Lessons from vintage cars, modular hardware, and enterprise software
✔️ Why the term “project” might be killing long-term software sustainability
✔️ The missing role in software teams: Should every company have a domain modeller?
Plus, they revisit last episode’s discussion on open-source maintainers going commercial, and Matt shares updates on his DIY gaming handheld.
💡 Is it possible to build software that stays modern forever? Tune in to find out.
🍻 Tonight’s Drinks:
Matt: Cherry juice (not red wine)
Liam: Archie Rose Single Malt 🥃
🔗 Links from this Episode:
Martin Fowler’s Tech Debt Quadrant
Eric Evans’ Domain-Driven Design
History of Open Source Forks (LibreOffice, OpenOffice, etc.)
Any 👍 Likes, 📣 Shares, 🔔 Subscriptions, and ❤️ Love go a long way to helping us continue this podcast.
Cheers! 🍻