Before 2015
Student, soldier, student again.
Before programming became the center, life had already left its marks: school, military service, internet shops, ordinary family life, and the question of what kind of future I wanted to build.
About
Huynh Nhan Quoc
Self-taught developer / Indie builder / Vietnam
I am a self-taught developer from Tam Ky, Vietnam. I learned programming by touching real things first: Blogger themes, small apps, coffee-shop software, affiliate websites, servers, SEO, tracking systems, runtime JS behavior, and eventually runtime design.
My work is not only about writing code. It is about reducing helplessness. I want to understand enough to build, operate, repair, and trust the systems I depend on. That road took me from Firebase and self-hosting to Go, Kitstack, Samdy, runtime JS, bytecode, VM, JIT, and now Kitwork.
Kitwork is the public form of a long private learning process. Before it had this name, many ideas lived inside Kitstack, the private foundation I used to build Samdy, shortlink, shortdomain and tracking tools, affiliate modules, customer pages, and small services. Kitwork is the cleaned and teachable part of those years.
Journey
Around 2015
Blogger and the first HTML question.
I started by editing Blogger themes, changing small pieces, breaking layouts, and learning that a website had a hidden structure behind what people saw. That first question never really ended.
University years
C#, a shoe-store app, and learning by rebuilding.
C# made software feel real. I learned through examples, translated code, mistakes, and the slow act of turning an idea into something someone could use.
2018
A friend's coffee shop and the Firebase night.
I helped a friend with a small coffee shop during the day and wrote software for it at night. When a Firebase update broke deployment, I stayed awake until around ten the next morning. Dependency became a physical experience, not only a technical word.
related article ->2019
Go, Ubuntu Server, and operating infrastructure.
I wrote Go for real work, learned Ubuntu Server and CLI, and began to see software not only as an app, but as the ground it runs on: processes, logs, files, routes, caches, and servers.
related article ->2020
Returning home, working as a shipper, and starting Kitstack.
I returned to Tam Ky with very little money, worked as a shipper, studied SEO and affiliate systems, and began building a private Go platform with Vanilla JS components. That platform became Kitstack.
related article ->2020-2025
The private Kitstack years.
Kitstack was not a public product. It was the private system I used to ship websites, APIs, templates, routing, customer logic, affiliate tools, and experiments. It carried real work, but also too much private business logic to be shared cleanly.
Samdy, the shortlink and tracking system, shortdomain redirects, affiliate modules, and many small sites were written on top of this foundation. They were the pressure that taught me what the platform had to become.
2021-2022
Samdy and proof that SEO could build real value.
Samdy combined Go, SEO, product data, affiliate tracking, and patience. It reached the Top 100 e-commerce websites in Vietnam, then taught me the cost of weak infrastructure: traffic, uptime, payment cycles, and server limits are not abstract problems.
related article ->2022-2023
Shortlink, shortdomain, and systems for growth.
The shortlink and shortdomain system was built to track affiliate links, redirect domains, campaigns, CPC, EPC, and traffic efficiency. It moved me from writing pages toward thinking in systems: measurement, routing, data, and automation.
related article ->2022-2024
Runtime JS, directives, and browser behavior.
I explored Web Components, directives, Proxy, DOM binding, and runtime JS behavior. Frontend behavior became runtime thinking: who owns state, who updates the DOM, and how small can the engine be?
related article ->Late 2025 onward
From private Kitstack to open Kitwork.
Kitwork is the attempt to standardize and open-source the useful parts of those private years: folder-based sites, runtime boundaries, templates, routing, bytecode, VM, JIT, and tenant isolation. It is the cleaned public form of lessons first tested in Kitstack, Samdy, shortlink systems, shortdomain redirects, and many private experiments.
related article ->What I believe
Slow understanding lasts longer.
I learned mostly by rebuilding, breaking things, and staying with questions until they became clear enough to use.
A system should be close to real life.
Servers, SEO, failed deploys, delivery work, coffee shops, and family life are not separate from the work. They shaped how I build.
Public work is a way to remember.
A repo, a note, an article, or a small explanation gives an idea an address. It makes private learning easier to return to and easier to share.
What I work with
Go
Runtime JS
Bytecode
VM
JIT
Templates
Multi-tenant
This site
Concepts answer: what is it?
Runtime, bytecode, compiler, VM, JIT, directives,
runtime JS, and tenant isolation.
Articles answer: why did I learn it?
Long essays, field notes, Substack posts, and
lessons from the road.
Projects answer: how did I build it?
Kitwork and other experiments as places where
ideas meet real pressure.