Dion Arifin smiling in front of a colorful wall

psst… nice to meet you ☺

{

"hi": "i'm dion", 👋

"loves": ["new friends", "good books", "tinkering online"],

"status": "grab a coffee & stay a while",

"next": ["say hi ☕", "get to know me ↓"]
}
scroll ↓

I TURN MESSY IDEAS INTO SHIPPED PRODUCTS.

i'm the developer you call when the idea is half-baked, the deadline is real, and nobody's sure where to start. i break the problem down, pick boring-but-solid tech, and get a working version in your hands fast.

front-end, back-end, the glue in between — i care about code that's easy to read, apps that load quick, and interfaces that don't make people sigh.

less talk, more commits. but also: clear updates, honest estimates, and docs your next dev will thank you for.

put me to work →

what i do

tools i reach for

work i'm proud of

a few projects that taught me the most.

01 ↗

desa piksel

an isometric pixel-art farming-village world you play in the browser — multiplayer, a built-in work log, chess, quests and a shared farm, all running on my own VPS.

  • Node.js
  • WebSocket
  • Canvas
  • Caddy
02 ↗

booking mobile app

a cross-platform app for scheduling appointments, with push reminders and offline-first sync.

  • Flutter
  • Firebase
03 ↗

public REST API

a documented, rate-limited API with auth, tests and CI — built to be boring and reliable.

  • TypeScript
  • Express
  • Docker
04 ↗

company website rebuild

a slow legacy site rebuilt as a fast static site — lighthouse scores went from red to green.

  • Next.js
  • Tailwind
  • Vercel

before you ask…

answers to the questions people usually send first.

01 when can you start?

usually within a week. if it's urgent, tell me — i'm pretty good at making room for interesting problems.

02 what kind of projects do you take?

web apps, mobile apps, APIs, dashboards, internal tools, and "can you fix this thing that's on fire" jobs. if it runs on code, let's talk.

03 how do you work best?

a clear goal, a single point of contact, and short feedback loops. i share progress early and often so there are no surprises at the end.

04 what's your favorite stack?

whatever fits the problem. i lean on TypeScript, React and Node, but i'd rather pick the right tool than the trendy one.

05 what makes you different?

i think like a user, not just a coder. i'll ask "why" before "how", and i'll tell you when a feature isn't worth building.

06 any weaknesses?

i will refactor your variable names if you let me. also, dark mode is not optional. 🌚

got a project in mind?

let's build
something good.