I care about systems and how we represent them — the layers, abstractions, and interfaces that shape what computers can do.
- Computer systems and architecture
- Memory, locality, and accelerators
- Representation and abstraction design
- System interfaces and boundaries
- Spatial computing
- Visual and interaction design, especially in earlier projects
pixelet · 2025–2026
A voxel world made from real-world terrain and places, to explore and build on, using Overture Maps and GEDTM30 elevation.
The eye decides how finely it is drawn: the view is divided into cells that each cover the same angular area around the eye, and blocks become coarser with distance to match. A pixel's ray, a walker's step and an edit all ask the same question — what fills this cube of space, at this level of detail — and one function answers it, so what you see is what you stand on.
A Rust core holds the world and draws it with WebGPU, as WebAssembly in the browser and natively on iOS and Android; the React Native UI decides nothing about the world. It runs on xpute.
This is also where I'm leaning on AI-assisted implementation the most, while focusing my own design work on the system architecture, representations, and boundaries.
xpute · 2026
A foreign function interface for the compiled part of a program. Its guest and host share nothing but the guest's memory and one kind of message: a frame that calls one method of an object under its handle. Interfaces are declared in WIT, with bindings generated for Rust, TypeScript and C++.
┌─ host side ─────────────────┐ ┌─ guest ── Rust / C++ ────┐
│ xpute: clocks, stop, log │ ══ link_in ══▶ │ the program's compiled │
│ program: objects, files, │ │ code, which owns nothing │
│ plugins and UI │ ◀═ link_out ══ │ but its memory │
└──────────────┬──────────────┘ └────────────┬─────────────┘
└──────────────────────┬──────────────────────┘
▼
┌─ the guest's memory ─────────────────────────────┐
│ frames: an object's handle, its method, a packet │
└──────────────────────────────────────────────────┘
xpute has three parts: the guest, host and link between them, drawn by WIT; the runtime that runs them on each platform and carries a UI on another thread; and the reusable kit beneath both. The same guest runs unchanged as WebAssembly in a page or as a native library on iOS and Android.
SCALE-Sim-PREMA · 2021
An undergraduate research project extending SCALE-Sim with PREMA (HPCA 2020), a preemption-aware multi-task scheduling algorithm for neural accelerators.
The implementation adds task scheduling, runtime prediction, checkpoint/resume, and mid-layer preemption to the simulator.
A from-scratch, user-level ELF64 loader, demand pager, and cooperative thread runtime for x86-64 Linux.
Written as a programming test for admission to a KAIST research lab, with no starter implementation. It builds process startup state manually, implements SIGSEGV-driven demand paging and cooperative user-level scheduling, and transfers control directly into loaded binaries.
Take-0 · 2015, 2022
A keyboard rhythm game inspired by DJMAX, originally written in Flash and later revived and ported from ActionScript 2 to ActionScript 3.
Along with the game itself, it includes a note editor and configuration tooling.
PIVOT · 2010–2014
My first long-running software project, started in middle school.
A widget-based desktop launcher built with Flash/ActionScript 2 — widgets snap to a grid across multiple pages, each with its own settings, inside a shared launcher UI.
It began as a quicker way to search the web and gradually grew into a small personal software environment.



