This site needs a wider screen
It is built for desktop and tablets in landscape for now. Please come back on a larger screen.
/ About · Ho Chi Minh City
I build and modernise the software a team runs its day on — moving a legacy PHP stack to React and Docker, ad tracking that has to reconcile at month's end, and the CV builder on this site.
4 of the things I shipped
Moved old Blade PHP screens to ReactJS, brought Docker into a workflow that had never used it, took part in the server migration, and proposed changes to how the team writes and ships code.
ReactJS · PHP · Docker · Linux
Owned the pipeline from the publisher page to the dashboards, and resolved the discrepancies and third-party measurement issues behind the monthly audit.
GSAP · DV360 · ReactJS · PHP
Role-based access for dealers, sales, sales admins and super admins; four document types moving through one approval state machine.
NestJS · TypeORM · ReactJS
Designed, built and run alone: edit a CV on the sheet itself, AI rewrite and review, one-link publishing, PDF export.
Next.js · Prisma · PostgreSQL
/ How I work
Tracking is only worth something if finance trusts it. I follow a discrepancy to where it starts — at AviviD that meant owning ad tracking from the publisher page to the dashboard the audit reads.
Bulk dealer email from an Excel upload took 40% of the admin work away. Approving a document stayed with a person.
Mentored 5+ interns on review standards at edtronaut.ai; they finished their tasks about 20% ahead of plan.
/ Working with AI
The model is fast and tireless; it is not accountable. So I moved up a level: I hand it the solution, I check what comes back, and I turn the team's rules into something it can reuse.
Receipt
This site is built this way: 8 skills in the repo carry its rules (migrations, tests, i18n, error codes), and 1,200+ tests stand between every change and production.
And from the other side: at AviviD I build RAG agents in Python and FastAPI — so I know where the model is strong and where it needs a fence.
Before any code: the problem, the constraints, the plan — which table, which rule, what must never happen.
Generated code is a draft until a test proves it and I have read it. I am the gate, not the typist.
Rules a team repeats become skills the AI follows on its own — so the next feature ships faster without being worse.
/ Background
Security degree, then servers, then full-stack. I still look after the machines my code runs on — this site runs on a VPS I set up.
Tell me about the team and the problem.