§ 00 / About me

Hi, I'm Trung
— a frontend builder.

I'm a frontend-focused fullstack developer based in Vietnam. I care about the small details: line-height that doesn't fight the reader, a checkout flow that doesn't lose the user, a Lighthouse score that holds up the day after launch.

Based in
Vietnam
Currently
VietnamBooking
Open to
Frontend / Fullstack roles
Languages
VI · EN (TOEIC 685)
Portrait of Nguyen Duc Minh Trung — Frontend-focused Fullstack Developer
Available · 2026est. 2024
§ 01 / StorySài Gòn → Vietnam 2019 — present

I started in Sài Gòn, finished as salutatorian, and now build interfaces for a Vietnamese OTA.

2019–23Sài Gòn · Uni

Four years at SaiGon University.

Information Technology, graduated salutatorian (2nd in class). A scholarship that funded the late nights and taught me to read English specs at speed, ship before deadlines, and argue politely about state management.

3.66GPA / 4.0
#2Salutatorian
4 yrsB.Eng. IT
2024EBIZWORLD · Fresher

The agency phase.

Fresher Fullstack at EBIZWORLD. The work was wide — landing pages, dashboards, the occasional CMS refactor — and that breadth turned out to be the point. I refactored React codebases I hadn't written, supported small AWS EC2 deployments, and learned to estimate honestly.

Jan–Oct2024
10 moTenure
React + EC2Daily stack
NowVietnamBooking · OTA

An OTA for Vietnamese travellers.

Since November 2024 I've been at VietnamBooking. The work is heavier and quieter: i18n routing for multilingual catalogs, Core Web Vitals that must stay green, booking flows where a misplaced spinner becomes a refund ticket.

I love it. Every megabyte costs someone a mobile plan, every redirect costs someone a flight. Performance, here, is empathy with a stopwatch.

Nov 2024Joined
OTABooking scale
GreenCore Web Vitals

The agency taught me to write code other people would inherit at 11pm on a Friday.

— On the EBIZWORLD year

Outside of work I read about engineering craft and write up things I learned — most of which end up on the blog.

§ 02 / VALUES

What I'd put on the wall.

Four ideas I keep coming back to — for code, for design, and for the small choices in between.

— 01

Be careful with bytes.

Every megabyte costs someone — a mobile plan, a server bill, a wait. Performance is a quiet form of empathy.

— 02

Ship the smaller thing.

A small thing in production teaches you more than a large thing in Figma. Then iterate.

— 03

Write it down.

Documented decisions outlive the people who made them. I write ADRs, READMEs, and changelogs like I'll forget — because I will.

— 04

Treat QA as a teammate.

Bug tickets are gifts. Triage them quickly, reproduce them carefully, and document the fix on the way out.

§ 03 / STRENGTHS

What I'm good at.

Honest skill levels — the bars below show how much I'd back myself in a real production decision today.

Next.js · App Router

2 yrs · daily driverNext.js · App Router: 92% proficiency

React / TypeScript

2 yrs · dailyReact / TypeScript: 90% proficiency

Core Web Vitals + SEO

Shipped on productionCore Web Vitals + SEO: 88% proficiency

Tailwind · shadcn/ui

2 yrs · shippedTailwind · shadcn/ui: 85% proficiency

NestJS · Prisma

1 yr · productionNestJS · Prisma: 75% proficiency

Vue 3 · Pinia

CMS scaleVue 3 · Pinia: 72% proficiency

PostgreSQL + schema design

Closure-table, RBACPostgreSQL + schema design: 70% proficiency

AI-assisted dev flows

Claude Code · CodexAI-assisted dev flows: 80% proficiency
§ 04 / WORKING STYLE

How I work with a team.

A short list — partly a checklist for myself, partly a "what to expect" if we end up working together.

  • Async-first, clear written updatesASYNC · 1
  • Write the PR description like a letterCRAFT · 2
  • Ship in small, reviewable chunksSHIP · 3
  • Open a ticket before you ping meFOCUS · 4
  • Pair on hard things, solo on easy onesPAIR · 5
  • Measure before optimisingDATA · 6
  • Leave the codebase tidier than I found itCARE · 7
  • Document the why, not the whatWRITE · 8
§ 05 / WHAT I'M EXPLORING

Where I'm headed.

Career goals I'm actively working towards — drawn straight from the things I keep choosing to learn next.

— I.

Senior frontend / fullstack.

Growing into a senior engineer on large-scale, high-impact products — the ones a real audience uses daily.

— II.

Performance & architecture.

Deeper expertise in Core Web Vitals, caching strategies, and system design that holds up under real production traffic.

— III.

AI & automation.

Leveraging AI agents and automation to improve engineering productivity — planning, coding, testing, documentation.

§ 06 / WHERE TO NEXT

Pick a door.

Three places to go from here.