Overshoot, then settle
Ship the ambitious version first, pull it back once it's real. Guessing scope in advance never worked for me.
Melbourne · Data Science @ UniMelb · est. 2006
I build things, ship them, then learn what I was missing.
Nine projects so far — storefronts, games, automation, motion graphics. Most started as a problem I actually had, and I learned whatever stack it took on the way.
2×
1st place — CISSA Codebrew & Design Blitz, as a first-year
9
Projects shipped end to end — design through deploy
203.6 kg
Waste collected leading a youth environmental committee
7.0
IELTS band · native Indonesian, fluent English
The shelf
Click a spine — nine volumes
How I build
Six habits, as physics
Momentum over planning
Two hackathon wins came from building in the first hour, not the third. Direction corrects easier than a stalled start.
Measure, don't guess
A game felt unfair until I instrumented it — time-per-kill was 8.0s. After balancing, 2.2s. Feelings aren't data.
Stretch to fit the stack
Shopify, Unity, WebGL, Remotion, C. I hadn't used most of them before the project that needed them.
Keep one thing at the centre
Every project orbits one real problem. A store that looked generic, a schedule nobody could read, a game I wanted to play.
Ship in phases
Storefront, then automation, then analytics. Four small releases beat one that never lands.
Proof
Receipts, not adjectives
Got something that needs building?
Open to internships, freelance builds and hackathon teams. Fastest way to reach me is email — I answer the same day.