Morten Larsen

Led the full migration of a legacy .NET 4.8 platform to ASP.NET Core 9/10 — a transition that had accumulated approximately a decade of technical debt. Delivered within 10 months. The work included architectural refactoring throughout, implementation of modern dependency injection patterns, and Infrastructure as Code via Bicep. The outcome was a codebase that could ship features again at speed.

The challenge was not the migration itself but the layered complexity underneath it: systems patched over systems, with original intent obscured. Solving that required understanding what the system was supposed to do — and finding the structure that would support it going forward.

Took ownership of a critical financial system that had been left in an unstable state by previous consultants. Conducted deep structural refactoring — reducing cognitive complexity, eliminating fragile dependencies, and restoring the kind of deterministic behaviour a financial system requires. New features were delivered alongside this stabilisation work.

Functioned in practice as the subject matter expert for the system, bridging the technical detail and the business requirements. Informally recognised as chief software engineer for the team.

Engaged by DTU's IT department to advance their Oracle Fusion ERP and EPM test automation programme. Early in the engagement, conducted an independent assessment of the existing tooling approach — identifying technical limitations, vendor dependency risks, and a trajectory that would not deliver the outcomes DTU needed. Presented findings to both IT and finance stakeholders, supported by a written analysis, and recommended a change of direction.

DTU acted on that recommendation. The subsequent implementation — a Playwright-based test suite, a custom React dashboard for visualising test results by business flow, and an Azure-hosted backend handling integration scenarios — delivered more in the remaining engagement period than the prior approach had managed over a considerably longer time. The team was left with a system they could understand, maintain, and extend independently.