Correctness before speed
A fast system that loses data isn't fast. I make the failure modes explicit before optimizing anything.
Software Engineer · Purbalingga
About
I care about the millisecond between a request and a result. Everything I build is measured against that gap — and the craft is the loudest part of it.
I started in backend development and never lost the habit of asking why a system feels slow. Today I work solo with a small group of product teams on APIs, data models, and the services behind them.
No agency layers, no account managers. You talk to the person designing and building it.
- BasedPurbalingga, ID · remote
- FocusBackend systems & API engineering
- ToolsLaravel, PostgreSQL, Redis, Docker
- StatusTaking 2 projects, Q2 2026
[ 01 ]
The path here
Nine years, in four moves.
- 2017
Backend developer
First production PHP services. Learned that correctness matters more than cleverness, and that logs are the only witness.
- 2019
Fullstack engineer
Owned features end to end — schema, API, and the front-end that consumes them. Learned that 200ms is a budget, not a hope.
- 2021
First product, solo
Shipped an internal tool end to end and spent a year learning what real users do to a "finished" system.
- 2026
Independent practice
Systems-heavy backends and the product surfaces on top of them. Two projects a quarter, on purpose.
[ 02 ]
What I believe
The rules I don't break.
Boring where it counts
Novelty belongs in the problem, not the stack. I pick technology that a team can still maintain next year.
No black boxes
If I can't explain why the pipeline is fast, it isn't finished. The same goes for what I hand over.