I build software that works — and I stay when it doesn't.
Most people have a story about a developer who delivered something, disappeared, and left them with a system nobody could touch. I'd rather be the other kind.
I scope the work in writing before you commit, tell you plainly what falls outside it, document what I change, and answer when you need me afterwards.
Eleven applications whose users couldn't log in
A business moving eleven interconnected ASP.NET applications onto modern .NET. The projects had been upgraded already but wouldn't connect to the database, and nobody could sign in - hundreds of existing accounts sat in an old authentication system that the new one couldn't read.
The obvious fix was to make everyone reset their password. I wanted to avoid that, because it turns one company's technical problem into an interruption for every person who just wants to log in and do their job.
Everyone kept the password they already had, and nobody noticed anything happened.
C# · ASP.NET MVC · EF6 to EF Core · ASP.NET Core Identity · SQL ServerA week of manual filing, removed from a legal practice
A lawyer filing legal aid reports by hand on a government portal - the same fields, from the same documents, over and over.
The harder decision wasn't technical. These are legal filings, so submitting them automatically would have been irresponsible even though it was possible. The extension reads the documents and fills the form, but presents an editable review panel first - nothing reaches the portal until a person has checked it.
A repetitive afternoon became a few minutes of checking, with a person still accountable for every submission.
JavaScript · Chrome Extension (Manifest V3) · document extractionRunning a platform that several companies depend on
Synapse is a workforce management platform I'm building to run in production on Azure - multi-tenant by design, so one deployment can serve multiple organisations: staff records, scheduling, a mobile client
Building it is one thing; making it production-ready is another. Broken database migrations, deployment failures and schema drift are the ordinary reality of software meant for real use, and dealing with them has been most of the work.
It taught me what it costs to be responsible for something people rely on.
C# · ASP.NET Core · EF Core · PostgreSQL · Azure