about
A little context behind the work.
I like software that is easy to use, hard to break, and still understandable after the first rush of shipping is over. That keeps pulling me across product engineering, systems work, privacy, machine learning, and low-level projects that sharpen the fundamentals.
story
I study computer engineering, but most of my learning has happened by making things until the rough edges become visible. That has taken me from full-stack product work into privacy systems, machine learning, protocol tooling, and the occasional hardware project.
What keeps me interested is the full arc of the work: how something reads the first time you touch it, how it is put together underneath, and whether it still feels sensible months later.
Open-source and self-directed projects are where I tend to go deepest. They let me follow an idea all the way down, then bring that discipline back into product work.
- what I do Product engineering across frontend, backend, applied ML, and systems-heavy builds.
- how I work I like clear structure, careful implementation, and products that still feel sensible months later.
- what matters Usefulness, reliability, and enough restraint that the work can speak without being overexplained.
principles
- Start with clarity, especially when the problem is complicated.
- Make the internals as considered as the interface.
- Avoid ornament that does not earn its place.
- Keep choosing work that teaches judgment, not just speed.
Interests
- Product engineering that stays close to real user needs.
- Systems, tooling, and privacy work where correctness matters.
- Applied machine learning with a concrete use case and boundary.
- Computer architecture and low-level work that sharpens instincts.
selected contributions
Linux / KUnit / 2026
Two KUnit tooling fixes accepted into the Linux kselftest tree.
I do not treat open source like a badge section, but it matters to me when the work earns its way into serious codebases. These patches came out of KUnit tooling, where small correctness issues have a habit of showing up at exactly the wrong time.
Both patches came out of small but real correctness issues in the KUnit tooling path. One is confirmed in current mainline Linux; the other is present in Shuah Khan’s kselftest `kunit` branch.
- copy caller args in run_kernel to prevent mutation February 26, 2026
- skip stty when stdin is not a tty February 27, 2026
- status Accepted via kselftest; one confirmed in current mainline Linux
- scope KUnit tooling / regression tests
- merged March 2, 2026