Maintainability

I shape codebases so teams can keep adding features without turning every change into a risky rewrite. The focus is modular boundaries, readable C#, predictable dependency flow, and practical conventions.

Layered systems

Clean Architecture and Onion Architecture to keep business logic isolated.

Team-ready code

Readable structure, Git habits, shared components, and clear project organization.

What This Covers

Clean dependency flow

API, Application, Domain, and Infrastructure boundaries inspired by the `api.onion` repository structure.

Reusable UI patterns

WPF MVVM structure, custom controls, and shared UI component libraries from ERP-scale work.

Repository patterns

Repository and Unit of Work patterns for maintainable persistence boundaries.

Long-term clarity

Object-oriented design, Git workflows, and practical documentation habits for evolving systems.

Related Stack

Clean Architecture5 years
MVVM5 years
Onion Architecture3 years
Git6 years

Related repositories

`api.onion` demonstrates Clean Architecture boundaries. `wpf.mvvm` demonstrates MVVM separation for desktop applications.

View api.onion