Dimas Pangestu
Serious about craft. Not so serious about myself.
Software engineer
4+ years in frontend, growing into fullstack product engineering.
Frontend foundation. Product curiosity.
About
not a studio. just me.I like figuring things out.
How a component can do more with less. Why a flow feels harder than it should. Where AI actually helps and where a good button is enough.
My background is frontend. My curiosity reaches into product decisions and fullstack AI. I like being close enough to the details to build, and close enough to people to know what’s worth building.
The longer résuméBlog / notes
open to revisionLoose thoughts. A notebook, not a manifesto.
A good interface leaves room for doubt.
Especially with AI. Show where an answer came from, make uncertainty visible, and let people change their minds. Confidence should be earned, not drawn as a shiny badge.
Reusable shouldn’t mean impersonal.
Components should remove repeated work, not erase context. A useful system makes the common things easy while leaving space for the unusual thing that actually matters.
The empty state is part of the product.
Before there is data, there is a person trying to get started. That moment deserves a clear next step, not a blank box and a shrug.
Long-form posts: placeholder. These are my existing notebook entries.
Stack
tools of the tradeExperience
real teams. real constraints.Infinity Wave Sdn. Bhd.Fullstack Developer, frontend-focused / MalaysiaJul 2025–Aug 2026
A clearer view of the data.
Making complex data easier to explore, with care for the interface and how it reaches production.
At Infinity Wave, my fullstack work leaned heavily toward frontend: React and Next.js dashboards, interactive charts with D3.js and Recharts, and configurable maps with Leaflet and Mapbox. I built shared components and traced slow rendering and unreliable data loading back to their causes, checking fixes in real use. Beyond the interface, I moved deployments from direct EC2 builds to containers using GitHub Actions, Amazon ECR, and EC2, keeping the app running through deployments and failed builds. I worked closely with backend and DevOps teams and documented the setup so the next developer could find their own footing.
Experience summary; no private project screens are reproduced here.
ChupFrontend Developer / Malaysia2024–2025
Making room for care.
Web applications built around healthcare workflows, not the other way around.
I developed and maintained applications with Vue.js and Nuxt.js, built reusable, documented components, and reviewed code for long-term maintainability. Working in a fast-moving team meant keeping implementation practical without losing the structure the next developer would need.
Product details remain private.
DafideaFrontend Developer / Indonesia2021–2024
Many projects. One thread.
Different clients and constraints. The same care for how an interface comes together.
At Dafidea, I worked on client projects including SEVA by Astra. I proposed reusable component structures, built responsive interfaces across browsers and devices, and worked closely with QA, backend, and frontend teams to deliver features aligned with business needs.
Experience summary; no private project screens are reproduced here.
Start with a hello.
A question, a half-formed idea, or something you’re making.