Skip to content
Jimmy Hwang

Six years of shipping. One live platform to prove it.

I build PartyX: six apps, payments, pipelines and the cloud under them, run by one person. On contract, you get that person for 6 to 18 months.

From Q4 2026 · Berlin or remote EU · 4–5 days a week · B2B invoice

The platform, in plain words

What one person runs.

Six apps

  • Guest appFind tonight, buy, show at the door
  • Host consoleCreate, sell, scan, get paid
  • OnboardingClaim your venue in minutes
  • Back-officeRefunds, payouts, the ledger
  • iOS appLaunching soon
  • Ingestion10,000+ events kept fresh, 8 cities

Underneath

  • Three databasesCore, search, back-office, kept apart
  • Object storageLike S3. Posters, images, caches
  • Queues with retriesEmail, images, tickets in the background
  • PaymentsStripe, checkout to refund
  • Automated releasesTested and shipped by pipeline
  • One person on callTwo years. No outsourcing

All of it runs on Cloudflare's global network. Five services, 300+ cities, no servers to patch. The same design ports to AWS or Google Cloud.

Built for 2026

AI writes the code now. The job is knowing when it is wrong.

Frontend

React, Next.js, Vue, React Native, design systems, realtime UI. The guest app and the industrial console.

Backend

APIs, data models, background jobs, payments, auth. Less time in Java and Go.

Cloud and operations

Cloudflare, Vercel, AWS basics, pipelines, monitoring. Not my lane: Terraform, Kubernetes, very high traffic.

The bottleneck moved

Review, not typing

With agents in the loop, pull requests run about 50% larger and wait around four times longer for a reviewer. I am the reviewer who also ships: agents draft, I own every line that reaches production.

Where agents fail

The unhappy path

They build the checkout that works and miss the refund that should not be allowed. PartyX's payments, payouts and refunds are exactly that code, live for two years with real money on it.

What one person means now

Deciding, not generating

Six apps in 22 months is not typing speed. It is choosing what to build, what to reject and what to delete, then carrying the pager for the result.

Why it matters 45% of AI-generated code ships with a known security flaw (Veracode, 2026). Somebody has to be the other half.

Proof

Check it yourself.

Stack TypeScript · React · Next.js · Vue 3 · Nuxt · React Native · Node · GraphQL · NestJS · PostgreSQL · SQLite · Stripe · Cloudflare Workers · Vercel · AWS · GitHub Actions · Python

Work

Two products in daily use.

PartyXFounder · 2020 – now
Problem

Small organizers could not sell tickets cheaply or be found.

Did

Built and run the whole platform: six apps, payments, ingestion, cloud.

50+ organizers, 10,000+ eventsOne operator, two years
Next.jsCloudflareStripe
WiTTRA NetworksSenior Software Developer · 2023 – now
Problem

Operators at airports and mines needed every asset live, without calling support.

Did

Own the operator Console end to end, plus the realtime API under it.

Used every shift at Arlanda, Eramet, ArcelorMittalContinuous releases since 2023
Vue 3NuxtGraphQL
2020 – 22
PartyX v1First version, first paying organizers
2023
Enklare, StockholmTypeScript / NestJS product work
2023 – now
WiTTRA NetworksIndustrial IoT console, remote from Berlin
2024 – now
PartyX rebuildSix apps, 6,000+ commits, nights and weekends

Start with two paid days.

One real ticket from your backlog. You see the code, the review notes and the questions I ask. Then decide.

Book a trial
Off the record

What the CV leaves out.

Before codeRan a 40-bed hostel in Montpellier for three years. That is where the product sense comes from.
LanguagesEnglish, French, Korean. German enough for stand-up.
Working styleDirect. Writes the decision down before the code.
Says no toSelling what I have not shipped.
Send a brief

The five things I will ask anyway.

Answer here, skip the first call. Written yes or no within one business day.

Prefer email? founder@partyx.info
Prefer a CV? One page, PDF

Goes to one inbox. Nothing else.