Projects that show systems thinking in practice

A business-facing booking product needs to handle guests, resources, times, staff roles, and conflicts without creating friction for the user.

I built a Laravel platform with public booking without accounts, admin and staff views, RBAC, tenant isolation, and transaction-safe booking conflict checks.

Shows that I can build systems where business rules, data model, and daily workflows need to hold together, not just a polished frontend shell.

Exchange rates need comparison over time with KPIs, charts, and risk indicators without heavy backend operations.

I built a monorepo with a React/TypeScript frontend and Python pipeline that fetches ECB data, publishes static JSON files, and updates daily through GitHub Actions.

Shows that I can connect data, CI, performance, and interactive UX into a solution that is easy to operate and reason about.

Visitors need to understand the course, setup, and contact paths quickly. The page needs to scan well, especially on mobile.

I built a React/Vite SPA with clear information hierarchy, focused CTAs, and responsive views that keep the content moving.

Shows that I can make content concrete, navigable, and technically easy to evolve without overdesigning the experience.

Tracking a round on paper gives you no data to improve from. Golfers need a way to log rounds hole by hole and get concrete feedback on what actually cost strokes.

I built a full-stack Next.js app with a hole-by-hole scorecard, localStorage persistence, statistics charts, screenshot import via AI vision, and Claude-powered coaching analysis per round.

Shows end-to-end product thinking: secure server-side AI integration, structured data from unstructured input, and a UI that stays usable during a round.