Remote contract engineering · Fractional technical leadership
I help teams stabilize and modernize business-critical software with practical architecture, maintainable .NET applications, and enough communication to keep technical teams, customers, and delivery goals aligned.
"We're stuck with technology when what we really want is just stuff that works."
Published author
Published by Manning, the book focuses on practical techniques for improving inherited applications: adding useful process, reducing pain points, separating concerns, and making existing systems more maintainable without assuming a clean slate.
View the book on AmazonI work best where technical debt, business rules, customer needs, delivery pressure, and practical architecture all meet. The goal is stability first, modernization with intent, and systems the people closest to them can understand, operate, and keep improving.
Modernize older systems in ways that reduce risk, respect delivery commitments, and leave the day-to-day team with code they can actually maintain.
Clarify boundaries, guide tradeoffs, and shape solutions around the people who will build, support, and use them every day.
Improve repeatability across cloud and on-premise environments with deployment workflows that make releases calmer and more predictable.
Build focused web applications with steady attention to usability, testability, long-term maintenance, and the business workflows behind the screens.
Work through domain-heavy systems across fintech, telecommunications, health care, transportation, lending, insurance, and other operational environments.
Use AI tools pragmatically to accelerate implementation, review, documentation, and refactoring without outsourcing judgment.
Support on-premise and cloud-hosted business systems with a bias toward reliability, observability, and clear ownership.
Move easily between engineers, customers, and stakeholders so the team solves the right problem in terms everyone can understand.
I care about systems that work in production and make sense to the people closest to them. That means practical modernization, clear communication, and technical choices that support stable delivery instead of adding theater.
Prefer steady, reversible improvements over risky rewrites. Stabilize the parts that matter, create room for change, and keep delivery moving while the system gets healthier.
Design around the capabilities, constraints, and daily realities of the people who will operate the system. A clever solution that the team cannot comfortably own is unfinished work.
Capture architectural and delivery decisions where the team can find them, with as much automation as practical. Good context reduces repeated debates and makes future tradeoffs easier.
Build release, support, and development habits that people can keep using after the urgent project phase passes. The best process is boring enough to survive a busy Tuesday.
Use tools because they reduce friction, reveal risk, or improve reliability. Automation, AI assistance, Docker, CI/CD, and documentation all earn their place by helping real work flow.
I’ve spent nearly all of the last 20 years working remotely with distributed teams, customer-facing groups, and business stakeholders. The common thread is practical delivery across organizations with real operational constraints.
I’ve worked with organizations of all sizes, from startups finding their footing to multinationals coordinating change across large teams and customer bases.
Older technical writing from earlier stages of my career. Some posts may be dated, but they remain here for reference.