How I ended up designing and building: a Bandung developer's path
I'm a developer and designer in Bandung, and people sometimes ask how someone ends up doing both. I'd rather show the path than narrate it, because the path is checkable. It's sitting in my Work page, with years attached.
The degree
I studied Computer Science at Telkom University, here in Bandung. It gave me the unglamorous foundation: how computers actually behave, which turns out to matter most when something breaks in a way the tutorial didn't cover.
It did not teach me how to make a store feel trustworthy at 11pm on a phone with a weak signal. That came from shipping.
The list, in order
Read the projects by year and a pattern shows up that I didn't plan.
- 2020 and 2021: online stores. Aza Wear, State Medical Equipment, Duma, HMNS, Green Rebel Foods. Storefronts are where design and code collide hardest. A product page is a layout, a performance budget, and a payment flow, all judged by a stranger in about five seconds.
- 2022 and 2023: the back of the house. A data dashboard, and BIONS by BNI. Less visible, more about systems, and a good reminder that most software is judged by whether it keeps working.
- 2024: both at once. More stores (Sonderlab, Nawaclo, Lakon Indonesia) next to a backend project, Combo.
- 2025: mobile. A split-bill app in React Native.
- 2026: back to the web, with more design in the brief. Adana in Next.js, Herotales, Speakez, Rawtype Riot, and Withavelle, where an off-the-shelf Shopify theme couldn't give the brand the polish it needed, so I built a custom one.
Looking back, the thread is clear: every project got better when the person deciding how it looks and the person deciding how it works were the same person.
Why one head beats two
When design and code live in different people, there's a handoff, and handoffs leak. A menu is drawn with a lovely animation, then simplified quietly because it stutters on a mid-range phone. I wrote about that in web designer vs. web developer.
If I'm the one drawing it, I find out it stutters while it's still cheap to change. That is most of my argument for doing both. It isn't that I'm better at either half than a specialist. It's that fewer decisions get lost between the halves.
What I'm not
I'm not an agency, and I'm not a large team. If a project needs ten people and a hard deadline, I'll say so and point you elsewhere. I'm also not neutral about the tools: I use AI for mechanical work and keep the decisions for myself, which I laid out in how I actually use AI.
Where this leaves me
Five-plus years in, I still think of myself as someone who builds things for the web and cares how they feel. The title "creative developer and designer" is just the shortest way to say that I won't hand you a drawing you can't build, or a build you can't stand to look at.
If that's the kind of person you want on your project, tell me what you're making. If you want to know more about me first, the About page is the short version.
Have something in mind?
Let’s talk