Hi, I'm Timothy — a fullstack developer who likes making old systems feel new again.
Two years of building software professionally, most of it spent rewriting a legacy enterprise app into something people actually enjoy opening. I work across the whole stack — API design and data on one side, the interface on the other — and I care about both ends equally.
Migrating a legacy internal application into a modern, elegant product — rebuilding the data layer and the interface side by side, and shipping it without disrupting the teams that depend on it daily.
Backend APIs for a pull-production and POS system that monitors the purchase-order process. Wrote the Postman documentation the frontend team integrated against, and sat with them through it.
A financial management web app: transaction and debt records, spending visualisation, and import/export. Containerised end to end.
A dockerised microservice music player — playback, search across songs, albums and artists, and artist uploads. Four services in four different stacks, talking to each other.
String-matching over DNA sequences to test whether a sample carries a disease marker, with a searchable history and a growing reference database.
I studied Informatics at ITB, and I've been building things on both sides of the API ever since.
I started out on the backend — production systems, purchase-order flows, the kind of software where a wrong number matters. That's where I learned to care about data models. These days I work fullstack, and the part I enjoy most is taking something old and heavy and giving it a second life: same logic, far better experience.
I like working close to other people — I spent two years assisting a networks course, and teaching turned out to be the fastest way to find out what I actually understood. Say hello if you're building something interesting.
Currently in Jakarta and open to fullstack roles — remote or on-site. I reply to everything.