A systems-focused engineer specializing in low-level debugging, kernel interactions, and C/C++ utilities. Demonstrates deep understanding of operating system internals—specifically regarding macOS linking behaviors, Linux kernel modules, and GDB scripting. Projects tend to be specialized developer tools or educational proofs-of-concept rather than polished consumer applications.
READMEs are consistently high-quality, explaining the 'why' and 'how' clearly, often better than the code coverage itself.
Scorecards highlight a consistent lack of automated tests across multiple repositories, relying on manual verification.
Many projects are marked as demos, proofs-of-concept, or student code, rather than maintained production libraries.
Good practices observed in tools like uniq-stacks (try/finally blocks) to preserve user state during crashes.
Demonstrates capability with kernel modules (cr3spy), header-only libraries, and low-level memory operations.
Expertise evident in creating custom GDB extensions (uniq-stacks) and dissecting complex linker behaviors (wtf-osx-dlopen).
Effective use of Python for building developer utilities and interfacing with C-level tools, though some syntax is dated.
Understands event loops and proxies (what-the-event, pproxy), though implementations are often experimental wrappers.
Experience with Linux Kernel Modules (LKM) and manipulating process page tables.
