About

Rote memorization doesn't work well for my brain. As a kid, I couldn't memorize poems or formulas without understanding how they worked. Later on, I cared much less about memorizing textbook definitions than understanding actual system behavior.

I think in data and state flow: Did the packet arrive? Did the socket read it? Did the application process it or silently drop it? Where did the assumption fail? Instead of memorizing interface steps, I check what the machine is expected to do, read the docs and --help flags, and trace the execution path.

I treat AI as extended memory and leverage. It handles routine syntax lookups and boilerplate while I focus on architecture, data flow, and root causes. Problems that typically stall on guesswork get diagnosed much faster.

I enjoy tackling problems that get dismissed as too messy or stubborn—from routing table edge cases on proprietary routers to elusive production bugs. I prefer uncovering the actual root cause rather than throwing more hardware or workarounds at broken code.

Strictly white-hat: clean, transparent engineering, privacy-respecting software, and solid system architecture.

When the war began, I left my home country to relocate, establish my own footing, and pursue software engineering full-time.

I treat programming as a practical craft. I pick up new tools and languages quickly, understand how they behave under the hood, and follow projects through to completion without romanticizing burnout.

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