Back home

The things I'm good at, in detail.

I approach full stack engineering as system design, not isolated feature development. Here's the system, and where my projects sit in it.

by the numbers

What actually shows up in the work

Instead of self-rated skill bars, here's how often each tool appears across the 14 case studies on this site.

Case studies using each tool

Counted from each case study's tags · out of 14

how I think about it

Five principles

Performance is designed, not debugged. Security is decided at architecture level, not patched later.

Scale early

Domain modeling, stateless APIs, indexing and Redis caching from day one.

Separate concerns

Rails for logic, React and React Native for UI, workers for async, infra for reliability.

API first

One API serving web, mobile, third-party and webhook clients.

Secure by default

RBAC, JWT / OAuth / 2FA, encrypted credentials, TLS and hardening.

Performance by design

N+1 prevention, code splitting, offline-first and CDN caching.

From database schema design to mobile deployment pipelines, I take ownership of the full software lifecycle. Systems that work today, and continue working reliably as they grow.

Ruby on RailsReact & Next.jsReact NativeMySQL / PostgreSQLRedisAWSDockerCI/CD Automation