Senior full-stack engineer in Nashville building Angular front ends (React when it fits), .NET back ends, and UX to the core. Currently building, and teaching AI agents good manners in production codebases. My favorite tools are still a scrap of paper and honest customer feedback.
Twenty-six years is a lot of shipping. These are the entries I'd dog-ear.
Here since before the first customer, and now it's profitable. Full-stack on a multi-tenant SaaS platform — Angular v21 and reactive state, ASP.NET Core on EF Core, ClickHouse behind tenant reporting. Alongside it: encoding the design system where coding agents actually read it, so what they generate lands on pattern instead of beside it.
Started the design system across business units and coded it — tokens, a component library, and the front-end architecture behind the MyTeam dashboard. Designers and developers finally worked from one source of truth, with usage guidance and handoff rules that made it stick past launch. Research kept it honest about what was worth solving.
Designed the member portal, then built it in .NET MVC — the front end and the controllers behind it. Led the Provider Portal redesign for 1M+ providers, grounded in on-site visits and interviews with the people using it every day. Took Bootstrap org-wide and sat in on UI decisions across 10+ teams.
also: I literally wrote the book — Idiot's Guide: Web Design with HTML and CSS
Not tools a project handed me — tools I've gone deep on. Front-end architecture for 20+ years; shipping .NET since the early 2000s.
Day to day at Kapoq: features end-to-end — Angular components and reactive state, ASP.NET Core APIs on EF Core, SQL Server schema, ClickHouse queries powering tenant-facing reporting.
From Classic ASP to coding agents. It's been a ride.
Persistence, curiosity, and an obsessive attention to detail define me — but the curiosity doesn't clock out. You'll find me under a dark sky, on a trail, or elbow-deep in watercolors.
The title matters less to me than the problem — front end, full stack, design systems, it's the same work from different angles. If you're wrangling a brownfield codebase, keeping coding agents on pattern, or figuring out what AI-assisted development actually looks like in production, that's a conversation worth having.