I build things that propagate — a message from one client to every other, a database row that repaints exactly one region of a screen, a signal that travels a graph the compiler can see end to end. Full-stack engineer working in TypeScript, and in the infrastructure underneath it.
Five products, each carried from schema to interface. Live links where the thing is public.
Group channels, direct messages, presence, typing indicators and read receipts. A TypeScript monorepo — Socket.IO API, Next.js client, MCP server and CLI — behind JWT auth and Nginx. Built and shipped solo.
Myanmar's first programming language. Reactive cells are syntax, not library — one dependency graph the compiler sees from database row to rendered pixel. Compiles to C, then to native binaries with arena memory and no GC.
Web search, PDF, OCR, document parsing and sandboxed code execution behind one SDK and MCP server — running entirely on your own machine, no third-party API keys. SSRF-hardened fetch perimeter, container-isolated execution.
Shipped and operated across web and app — the FastAPI backend, the TypeScript product and marketing frontends, and an editor plugin that puts the authoring workflow where writers already are.
Paired client and admin apps on a Go REST API, sharing a single design-system package — auth, store, subscriptions, moderation and analytics — with a Python service handling AI orchestration.
The idea behind LukeLang, running here. Move a source cell — watch the change travel the edges and repaint only what depends on it.
Three derived cells, one dependency graph. Nothing polls and nothing subscribes — the edge carries the change, and only the cells downstream of it recompute.
I am a full-stack engineer from Myanmar, currently Lead Developer at Boardwalk Labs, where I own architecture and delivery across web and mobile while finishing a B.Sc. in Information Technology.
I work best where the whole problem is mine — schema, API, interface, and the Docker and Nginx underneath. Most of what I know came from shipping: a real-time platform, a self-hosted agent toolkit published on PyPI, and a compiled language that exists because I wanted to know whether one dependency graph could really run from a database row to a pixel.
I build in public. Everything above is on GitHub, and I would rather be judged on it than on a bullet list.