Professional work

Enterprise systems

Most of my day-to-day work is on internal enterprise .NET systems. The code stays private, but the kind of work doesn't.

Private workArchitect, designer, and developer

Overview

These are systems people rely on every working day, where the rules come from policy and law, the data is sensitive, and the software has to keep running while it changes underneath them.

Highlights

A data management and reporting platform delivered end to end in under three months: architecture, development, CI/CD, hosting, and secure deployment
A scheduling application that serves several facilities from a single deployment, built with Clean Architecture and separate read and write paths
A platform of .NET microservices with Angular micro-frontends, organized around Domain-Driven Design boundaries
Shared security libraries, published as NuGet and npm packages, so every application handles authentication and permission-based authorization the same way
Read-only REST APIs over large existing databases

Get in touch

Let's talk about software, architecture, or the book.

Whether it's a question about a chapter, an invitation to speak, or a design problem you're working through, I'd like to hear about it.

Connect on LinkedIn