OZ Coding School

MovieGet Movie Ticketing Site

As the lead of a 3-person team, I handled payments and deployment, and doubled as the person who clears blockers wherever the team got stuck.

Role: Team lead · Payments · Deployment
Period: 2024.10 ~ 2024.11
Stack: ReactTypeScriptViteToss PaymentsAWS

CLIENT

React + ViteBooking UI, infinite scroll

EXTERNAL

TMDB APIMovie data

Toss PaymentsPayments

DEPLOY

AWSStatic hosting

App / clientNativeServerWorkerStorageExternal

Movie data from an external API, payments through Toss, deploys on AWS; the lead also owned merges and build recovery.Hover a block to highlight its flows. Drag to pan.

Outcome

50%
Share of commits in a 3-person team (185 commits, ranked 1st)

01What it is

A movie ticketing site. It pulls movie data from the TMDB API, integrates payments with Toss Payments, and is deployed on AWS. As team lead, I took charge of integration merges and recovery whenever the build broke, and I also handled the infinite scroll refactoring for listings myself.

02Outcome

I authored 185 commits, 50% of the total. More than the number itself, this project taught me that a team lead has to double as the person who clears blockers for teammates to keep the project moving.

GitHub