My day-to-day is the unglamorous, high-stakes work that keeps a business running: SQL performance, defensive backend services, third-party integrations, and a quiet front-end modernization done page by page so production never blinks.
I'm currently leading the migration of a long-running .NET Framework 4.5 / WebForms stack to .NET 8 / Razor Pages — three modules already in production with modern authentication, responsive design and a clean architecture. The legacy and modern stacks live side by side, with zero disruption to the operations team.
I think in terms of business impact: how much time a slow report wastes every week, how a single deadlock blocks invoicing, how a fragile API integration costs the support team. Then I fix it — properly, with tests, audit trail and rollback paths.
Architecture-first
Every module I ship has a clear layering, defensive boundaries and an audit trail. No hidden globals, no surprise side effects.
Performance under real load
Query plans, indexes, isolation levels, transactions — I optimize where it matters, measured in milliseconds saved per production run.
Modernize without regression
Legacy doesn't mean rewrite. I migrate by additive layers — old and new in parallel, page by page, never a broken production morning.