.NET application development

Most of my work has been on applications that were already running: picking up someone else's codebase, fixing what broke, and adding what was missing. I've been building on .NET and C# since 2005.

The work

What these projects involve

Maintenance and fixes

Keeping a working application working: bugs, breakages, and the things that have been on the list too long.
New features

Adding to a live system without a rebuild, and without breaking what already works.
Integrations

Connecting an application to the other systems around it: payments, membership, events, third-party services.
New builds

When a new application is the right call, built on ASP.NET Core and made to last. This site is one.

The systems

What they usually look like

Applications an organization runs on and can't switch off: membership platforms, internal systems, customer-facing sites. The common thread is that the code already exists and someone has to be able to read it, work in it, and leave it in better shape than they found it.

The hard part

The back end, not just the front

Plenty of people can put up a page. Fewer can build what sits behind it: the database, the business logic, the system that actually solves the problem. That's the work I've spent my career on, and it's where a real application pulls ahead of a template.

That includes AI where it earns its place. I built AI into a live product, Jambalam, using Azure AI to power a working feature people use, not a demo.

Proof