/ Deployed Systems

Code that ships. Endpoints that hold.

Four back-end projects. Each one live, documented, and open source. Stack choices are explained, not assumed.

Close-up of a laptop screen showing a PostgreSQL schema diagram with table relationships, cool blue ambient light, dark desk surface, no person visible
Close-up of a laptop screen showing a PostgreSQL schema diagram with table relationships, cool blue ambient light, dark desk surface, no person visible
Terminal window showing JWT token decode output and curl request-response log, green and cyan monospace text on dark background, screen glow, no person
Terminal window showing JWT token decode output and curl request-response log, green and cyan monospace text on dark background, screen glow, no person
Wide shot of a deployment dashboard on screen showing green build status indicators and environment variable config panel, cool screen glow, dark ambient, no person
Wide shot of a deployment dashboard on screen showing green build status indicators and environment variable config panel, cool screen glow, dark ambient, no person
Close-up of a Docker Compose terminal output showing service startup logs in monospace, cyan and white text on near-black background, cool screen glow, no person visible
Close-up of a Docker Compose terminal output showing service startup logs in monospace, cyan and white text on near-black background, cool screen glow, no person visible

UI · BRAND DESIGN · FIGMA

Solar Smart

Brand identity and design system for a renewable energy company

UX · DESIGN THINKING · RESEARCH

Eco Travel

Sustainable travel app built with design thinking methodology

JAVASCRIPT · HTML · CSS

Reception Management

Delivery tracking dashboard with real-time late alerts

NODE.JS · EXPRESS · MYSQL · JWT

E-Commerce System

REST API with JWT auth, MySQL database in 3NF, admin front-end with ExpressJS

REST over GraphQL: every project has fixed, predictable access patterns. GraphQL's flexibility introduces surface area that isn't needed and isn't tested.

— Architecture Decisions

Choices documented, not assumed.

Relational databases as the default: foreign-key constraints and transactions enforce data integrity at the schema level, not in application code.

Deploy targets chosen for reproducibility: Railway and Render provide environment parity with minimal config drift between local and production.

All repositories are public. Source, tests, and deploy config are in the same place.