Staying Up to Date

We migrated Konstrukt with enthusiasm and a certain degree of naivety. Future technical debt in our ASP.NET Core services wasn’t on our mind back then, and we certainly spent little energy thinking about future maintenance. Shortly after the migration, a fresh release of ASP.NET Core emerged, and we were suddenly faced with a substantial amount of work if we wanted to maintain our up-to-date status. We lagged two versions when we did the second migration, and there were several breaking changes that had been announced well in advance – that we could have been prepared for.