Melbourne · Data Science @ UniMelb · Est. 2006

Nine projects,
and a habit
of finishing them.

I'm Aufan. Storefronts, games, automation, motion graphics — most of them started as a problem I actually had, and I learned whatever stack it took on the way out.

Say hi

Drag the top card off the pile. Or click it to open the full entry.

0 Projects shipped end to end — design through deploy

0× 1st place — CISSA Codebrew & Design Blitz, as a first-year

0kg Waste collected leading a youth environmental committee

0 IELTS band · native Indonesian, fluent English

The collection

Tap a card to turn it over · nine entries

How I actually build

Four rules I earned the hard way

01

Ship it, then find out what I was missing.

Every project on this page started before I knew the stack. Shopify Liquid, Unity, Remotion, serverless functions — all learned mid-build, because a half-finished thing teaches more than a tutorial.
02

Measure it instead of feeling it.

Our co-op game felt hard. Instrumenting the combat loop showed why: a duplicate component had halved player health. Time-per-kill went 8.0s → 2.2s once there were numbers to argue with.
03

Automate the part I'd quit over.

The storefront didn't die from the build, it nearly died from posting daily. So the posting became a pipeline that sources media, prices it, and never repeats a listing.
04

Look at the thing before calling it done.

"It compiles" is not verification. I shipped a dungeon four separate times with the grass rendering solid black, because nobody — me included — had actually opened it.