Five years of professional design work — brand systems, packaging pipelines, retail environments — gave me something most developers don't start with: the instinct to think in systems before writing a single line of code. When I moved into software, I didn't start from zero. I came from years of mapping business processes, coordinating cross-functional teams, and understanding what users actually need. The result: 100K+ lines of production TypeScript across four major projects — all shipped and running.

I build with AI assistance and I'm straightforward about it. Every project in my portfolio was developed through human-AI collaboration. But architecture decisions, domain modeling, database schema design, and system integration — those come from hands-on experience coordinating enterprise software development and deeply understanding the business domains I build for. AI accelerates the how. Knowing the what and why is what separates a developer from a prompt writer.

Designing an 83-model ERP schema with FEFO/FIFO stock picking and atomic reservation transactions requires living inside the business processes it automates. Implementing triple OAuth with custom PKCE S256 requires understanding security trade-offs, not just following a tutorial. Building a 3D game engine where every model is procedurally generated from code requires genuine problem-solving at every step. What I bring is the ability to translate complex real-world domains into production software — and the design background to make it usable.