Yanuar Aditia

Product engineering,
from unclear to shipped.

I set technical direction, stay close to the code, and connect product intent to systems that a team can operate. TypeScript is my strongest workflow. Go and other languages join when the problem asks for them.

Role
Principal Engineer
Mode
Team or independent
Base
Indonesia · UTC+7
Portfolio macro pad

W / O / B / E / T

Principal scope

I work across the decision chain.

01

Find the product constraint

Turn an ambiguous request into a problem the team can reason about and validate.

02

Choose system boundaries

Shape APIs, data flow, ownership, and delivery paths around the real operating model.

03

Make the workflow executable

Build the TypeScript path, service, tooling, or Go component needed to move the work.

04

Leave the team stronger

Document decisions, improve developer feedback loops, and remove recurring friction.

Selected systems

Evidence from product to platform.

Open the work archive

Command navigator

Ask the site where to go.

Real commands, real destinations. Type help to reset the map.

help

Commands: works, oss, blogs, github, email, clear

Field notes

Decisions worth writing down.

Read every note

Why using Nuxt.js?

A heartfelt journey of how our team transformed from jQuery warriors to Nuxt.js advocates. This is the story of letting go of our legacy baby and embracing a future that scared and excited us at the same time.

Read note

New Domain, New Chapter

A new domain, a new beginning. This blog post marks the start of my journey with a fresh domain and a renewed focus on sharing knowledge and experiences.

Read note

Open channel

Have a technical problem that crosses product and architecture?

Send the problem, the constraints, and what is currently blocked. I will reply from me@yan.ad.