I build and maintain production business systems — leading a Blazor-to-React migration, validating API contracts, reviewing code with merge authority, and troubleshooting CI/CD and integration issues across a four-person team. I also design and ship independent full-stack products, including a browser-based tool with 3,000+ users sustained over two years.
|
The core tools and frameworks I use to build production web applications.
.NET 8, Blazor Server, and C# powering production business systems — quoting, tracking, and document workflows for a 4PL logistics platform.
React, TypeScript, and Vite for component-driven UIs. I build fast, type-safe front-ends for web applications and side projects.
REST API integration, contract validation, and frontend/backend coordination — plus client-side state management and persistence across Blazor and React.
Automated build verification and regression testing using Selenium WebDriver (C#). I've owned QA pipelines that ship code with confidence.
Responsive layouts, accessibility basics, and form-heavy workflow design. HTML, CSS, Tailwind, and Bootstrap — I embrace the front-end.
GitHub Actions for CI/CD, Netlify and Azure deploys, and hands-on troubleshooting of pipeline failures, deployment issues, and environment and service connectivity problems.
The technical environments and architectural concerns I navigate day-to-day in production development.
Coordinating work across Blazor and React front ends, .NET APIs, and shared business logic — keeping quoting, tracking, and document workflows consistent as the platform migrates piece by piece.
Validating API contracts between frontend and backend, catching breaking changes before they ship, and keeping request/response shapes honest as endpoints evolve.
Tracing CI failures, deployment issues, environment misconfiguration, and service connectivity problems back to root cause — not just the frontend symptom.
Push-based automated front-end testing, regression coverage, and QA pipelines designed to keep production deployments stable.
CI/CD workflows using GitHub Actions, Azure hosting, and Netlify deploys for consistent, repeatable release pipelines.
Reusable Razor component systems, client-side tool modules, and local-first persistence patterns built for long-term feature expansion.
Reviewing pull requests with merge authority, flagging architectural concerns and dependency risks before they land, and using AI-assisted review to raise the quality bar on production changes.
Evaluating new dependencies and architectural tradeoffs, weighing long-term maintainability against short-term velocity for a platform in active migration.
These are the products I actively maintain today, spanning production UI architecture, client-side tooling, and full-stack application design.
Multi-tenant, permission-aware campaign encyclopedia and continuity manager for tabletop RPGs — full-stack SaaS with field-level authorization, wiki-linked entities, and audit history.
Permission-aware campaign continuity platform for TTRPGs — multi-tenant SaaS with entity relationships, revision history, and campaign-scoped authorization. Live on Railway.
Full-stack financial planning platform with clean layered architecture, debt projection, scenario comparison, budgeting, exports, and production deployment on Railway.
Privacy-first financial planning platform with debt payoff simulation, scenario comparison, budgeting, exports, and credit projection — shipped as a full-stack product on Railway.
Browser-based tabletop RPG suite: initiative tracking, a lightweight battle map VTT, character management, encounter building, and a Notion-style campaign journal — all local-first and offline-capable.
Modular browser-based tabletop toolkit — initiative tracking, battle map VTT, and campaign journaling with local-first persistence.
Client-side PDF toolkit: view, merge, split, edit pages, convert images, compress, and sign — no file uploads. Eight independently-scoped tools sharing a modular client-side architecture.
Privacy-first PDF toolkit: view, merge, split, sign, convert, and compress — entirely client-side, no uploads, no backend.
Smaller experiments and UI prototypes. Older work; included for completeness.
Open to full-stack and frontend-focused engineering roles involving React, TypeScript, .NET, enterprise software, and technical ownership.
