Engineering the system.
Considering the risk.

I build web applications and supporting systems that connect interfaces, data, and workflows. The decisions underneath — how responsibilities are divided, how data moves, and how failures are handled — deserve the same attention as the screen.

• Full-stack web applications and responsive interfaces
• API integrations and community workflows
• Data models, validation, and application state
• Maintainable components and clear system responsibilities

My cyber security background informs how I think about identity, permissions, and the information a system handles. In my projects, that thinking appears in access checks, separation of internal and public data, validation, and traceable actions.

• Authentication and permission boundaries
• Server-side validation and considered data handling
• Separation of public, member, and staff information
• Audit history and visibility into sensitive actions

I’m interested in what happens between systems: collecting information, detecting changes, and getting the right signal to the right place. Monitoring and automation make that work visible.

• Monitoring, snapshots, and historical context
• Change detection and notification routing
• Discord integrations and focused automation
• Custom game systems and practical utilities