Selected systems, not isolated screens.

Work where architecture, interface, data, and delivery had to support the same product outcome.

NOUS

A public product presence and custom content platform built to express the company clearly and remain straightforward to operate.

Constraint: NOUS needed a modern web presence that matched the quality of its work without creating a fragile marketing stack.
Decision: I selected Astro for a fast, maintainable front end and connected it to a custom CMS and APIs that I designed around the company's publishing workflow.
Responsibility: CTO, technical direction, architecture, front-end delivery, CMS and API development.

Visit projectPrivate source

A focused CMS built around the way the team actually publishes, edits, and evaluates content.

Constraint: Existing systems did not fit the publishing workflow or provide the useful operational statistics the team required.
Decision: I designed a dedicated editorial model with clear editing flows, content monitoring, typed APIs, and delivery optimized for Astro projects.
Responsibility: Lead developer and system architect.

A responsive system for daily patient intake, appointments, clinical records, and secure access.

Constraint: Patient movement and clinical information were tracked manually, which made daily coordination and record continuity difficult.
Decision: I separated the React client and Express API into independent repositories so authentication, interface work, and backend behavior could evolve without coupling releases.
Responsibility: Lead full-stack developer.

A fast, image-led portfolio with a managed gallery for a professional nail artist.

An Express API with CRUD operations, role-based access, authentication, and transactional email.

A typed Fastify API for posts, categories, views, protected writes, and test-backed content operations.