About

Rote memorization doesn't work for my brain. As a kid, I couldn't learn poems by heart or remember which scientist proved which theorem. Later, I never bothered memorizing the formal names of the OSI layers.

I think in behavior: Did the packet arrive? Did the socket read it? Did the app process it or silently drop it? Where did state break? Most people memorize which buttons to click. I check what the machine is supposed to do, read --help, and trace the execution.

AI acts as extended memory. It handles syntax lookups and boilerplate while I focus on architecture, state flows, and root causes. Problems that take days of blind guessing get diagnosed in hours.

The more people say a problem is impossible—or when support says “just buy a new server”—the more motivated I get to fix it. From loading custom routing tables into closed, proprietary routers to debugging silent production crashes, I prefer finding the actual root cause over throwing hardware at bad code.

Strictly white-hat. No gambling, no betting, no gray-zone schemes, no infobiz. Just clean, legal engineering and R&D.

I started from scratch. When the war began, I left my home country to build my life on my own terms and pursue software engineering full-time. No safety net, no excuses.

I don't sleep on my laptop or romanticize burnout. Programming is a craft. I pick up new tools and languages quickly, understand how they work under the hood, and finish what I start.

Based in Da Nang, Vietnam. Available for troubleshooting, architecture reviews, and engineering roles on teams solving hard technical problems.