I build systems that actually get used.
Full-stack developer focused on booking systems, scheduling logic,
and clean UI.
About
Learning by shipping, not by collecting tutorial clones.
I care about what systems do under pressure: conflicting bookings,
late updates, uneven demand, and the edge cases that show up once
people actually use the product.
-
Real-world systems: booking flows, scheduling rules, and dashboard
operations.
-
Backend logic first: state transitions, constraints, and predictable
behavior.
-
UI that stays clear under load: practical, minimal, and easy to
operate.
Projects
Built as systems, presented as case studies.
Featured System
Clubly
Online event registration and club operations platform for
student-driven college communities. Built to handle real event
lifecycles across departments, roles, groups, payments, and
points, without turning admin workflows into manual chaos.
Event Management
Clubs and Roles
Groups and Teams
Leaderboard and Points
Payments
Institution Auth
Operations
Create, schedule, register, mark attendance, and publish
event outcomes in one flow.
Access Control
Role-based permissions across Admin, Core Member, Volunteer,
and User boundaries.
Engagement
Gamified points and rankings with college-wide and
club-specific leaderboard views.
Reliability
Payment verification, mail notifications, and protected
routes to keep state consistent.
01Club admin creates event and registration
constraints.
02Users join individually or through code-based groups.
03Attendance is marked and winners are assigned.
04Points and leaderboards update with audit-friendly
behavior.
Users
450+
Groups
300+
Registrations
250+
Payments
190+
Events
15+
Logic-Heavy System
Telemedicine Queue Optimizer
Priority-based scheduling for telemedicine that balances urgency
and fairness. The queue is not first-come-first-served by
default; it is explicitly scored and tuned.
- Weighted scoring: severity, wait time, and fairness.
- Dynamic fairness boost to prevent starvation.
-
Configurable thresholds and weights for different care
settings.
- Deterministic ranking plus simulation-friendly output.
| Method |
Patient Order Snapshot |
Behavior |
| FIFO |
P2 -> P3 -> P1 |
High urgency can wait too long if they arrived later.
|
| Optimized |
P1 -> P2 -> P3 |
Urgent cases surface quickly, with fairness increasing
over time.
|
Low-priority patients eventually surface, by design.
Skills
Stack I use to ship practical systems.
React / Next.jsFrontend
HTML / CSS / JavaScript / TypeScriptWeb Development
Node.jsBackend
MongoDBDatabase
Google OAuth + Role-Based AccessAuth & Security
Java / C / C++ / PythonCore Languages
Data Structures & AlgorithmsProblem Solving
System DesignScheduling, queues, dashboards
UI/UX + FigmaDesign Systems
Vercel + Git-Based DeploymentsShipping
Thinking
Behavior over decoration.
I care more about system behavior than visual tricks.
Edge cases matter more than happy-path demos.
I prefer simple, controllable architectures over fragile
overengineering.