About
About me
Information Systems student at Gunadarma University, building web and Android apps since 2025.
Background
I started with the web because it was the fastest way to see something I built being used by someone who wasn't me. Android came later, when I wanted to understand what happens when there is no server to fall back on. Both taught me the same thing: the interesting part isn't the framework, it's deciding what the data should look like before writing any UI.
How I think about code
I try to pick the boring option first. Most of the complexity I've had to undo in my own projects came from solving a problem I didn't have yet.
Types before abstractions
TypeScript and Kotlin let me state a rule once instead of re-checking it in every function. I lean on that before reaching for a pattern.
Fast by default, not by a later optimisation pass
Server components, incremental static regeneration, and correctly sized images get most of the way there without a performance sprint at the end.
Built for the person who has to use it
The Pempek Cek Lis admin panel exists so the owner never has to message me to change a price.
How I work
Roughly the same loop on every project.
- 1Talk through what the person actually needs, which is usually narrower than the first request.
- 2Model the data first: tables, relations, and who is allowed to read what.
- 3Build it, using types as the contract between layers.
- 4Test on a real phone and a slow connection, not just on my laptop.
- 5Ship it, then fix what actually breaks.
What I'm looking for
A part-time internship or freelance projects where I can work alongside more experienced engineers and have my code reviewed properly. I have around 20 hours a week free and can start immediately. Full-time has to wait until I graduate, but I would rather learn on a real team than keep building on my own.