About.
Full-stack web developer, lately building agentic LLM workflows. Also games, LoRaWAN fleets, and data at scale. Fast because I read the platform; readable because someone has to maintain it, and I only ship what I can explain to myself. Work page has the long version; this is the short one.
Off the keyboard.
I like meeting people, hearing how they got where they are, and talking shop. Most of what I know got there because someone else explained it first. Decisions I take slow: they tend to be better after someone's had a chance to argue with them.
Tools I reach for, and when.
-
Node
Default for anything web-shaped on the server side. The stdlib is most of a framework, if you bother to read it.
→ servers · tooling · scripts -
Web
The browser is the system. First paint, prefetch, View Transitions, view-source: most of what you need is already in the platform once you read the docs. Vue 3 or React when a framework actually pays for itself.
→ first paint · prefetch · view transitions -
Zig
For write paths that have to be deterministic. No hidden allocator, no surprises. Comptime makes hand-written serialization worth the typing.
→ hot loops · parsers · binary formats -
Rust
For games and high-performance systems. Same ground as C++ and Unity C# in shipped titles. Rust doesn't let you skip the parts that bite later.
→ games · high-performance · systems -
LLM agents
For work that's open-ended but repeats. I wire agents into pipelines with deterministic orchestration around them and review gates that have to pass before anything ships. The model does the fuzzy part. The harness keeps it honest.
→ orchestration · review gates · continuous delivery
If you're hiring for someone who cares how it's built as much as that it ships: linh@lelinh.dev, codeberg.org/litozor (or its GitHub backup, when it's working), or LinkedIn. Or start with the work page.