● BUILD MODE — hover left / right to switch ● ARCHITECT MODE — systems over pixels
WEB DEVELOPER SOFTWARE ARCHITECT
Halo, saya TEINSISUNO.
Saya membuat web yang membuat orang berkata “wah”, lalu membuat sistem di belakangnya supaya tidak berkata “waduh”.
Make it look good. Make it work properly.
◀ THE WEB DEVELOPER
“Make it feel good.”
UI · INTERACTION · FRONTEND
ANIMATION · PERFORMANCE · A11Y · UX
THE SOFTWARE ARCHITECT ▶
“Make it survive.”
ARCHITECTURE · BACKEND · DATABASE
API · SECURITY · SCALABILITY · INFRA
SCROLL TO DEBUG ↓
Yes, this animation uses JavaScript. No, it wasn't necessary. Yes, I still made it.
SELECTED WORK
Multi-unit operational dashboard without duplicated logic.
Finance workflow users finish in 2 steps, not 7.
Academic system: grades, attendance, and sanity.
Queue system with realtime display and zero drama.
VISIBLE
INVISIBLE ×
Good software is not only about what users see. It is also about everything they never have to think about.
THIS LOOKS COMPLICATED. GOOD. THE ACTUAL SYSTEM ISN'T.
HOW I BUILD
01
Before writing code, I try to understand what the actual problem is. Yes. Sometimes this takes longer than writing the code.
02
Sketch the flow users actually take, not the flow we wish they took.
03
Draw the boring boxes: client, web, API, service, database. Decide what can fail safely.
04
Small slices, working software every week. No big-bang rewrites.
05
Happy path plus the weird path users will definitely find at 11pm.
06
Boring deploys: migrations first, feature flags, rollback plan.
07
Logs, metrics, and listening to the humans who use it daily.
…AND THEN
REPEAT
Software is never done. Only deployed.
THE LAB
Sometimes I build things simply because the browser can do something ridiculous.
ENTER THE LAB →4,209+
BUGS FIXED
*playful stat, not a claim
∞
COFFEE CONSUMED
*playful stat, not a claim
47
TABS OPEN
*playful stat, not a claim
312
DEPLOYS SURVIVED
*playful stat, not a claim