When they asked me what makes software maintainable, I shared a core belief: I always push for simple over clever. The goal isn’t just getting code to work—it’s making sure it stays easy to understand, fix, and grow. To support that, I set up clear standards across the board: consistent naming, formatting, folder structure—you name it. We back it up with tools like SonarQube to catch quality issues early in the cycle. One thing I emphasize with my teams is modular thinking. We break down problems into small, focused components, which makes it easier to test, reuse, and update without side effects. Docs and comments? Non-negotiable. Especially around tricky APIs or complex logic. If we can make things easier for the next dev—or even our future selves—it’s a win. I also carve out time for regular cleanup and refactoring. Technical debt isn’t something I ignore; we log it, track it, and treat it like any other work item. And automation plays a huge role. I’ve built CI/CD pipelines using Azure DevOps and Jenkins that handle builds, tests, and deployments—keeping everything smooth and reliable. At Image Solution, I led the team behind a cloud-native healthcare analytics platform built on .NET, Azure Functions, and Angular. We designed it to be modular and future-ready from the start, with CI/CD and quality gates baked in.