Engineering Profile
How I think about
engineering.
I care about systems that run efficiently, software that doesn't leak, and architectures that make sense at 3am when something breaks. I work across the stack from kernel modules to REST APIs — not because I'm spreading myself thin, but because understanding how things connect at every layer produces better decisions at every layer.
Systems & OS
RustCLinux kernel
eBPFkernel modulesprocess sandboxing
ARM / x86
Android
AOSPBinder IPCZygote
JNIZygiskHAL
fastboot / recovery
Backend & APIs
GoNode.js (ESM)WebSocket
HTTP/2async I/OPostgreSQL
Redis
Cryptography & Security
WebAuthn / FIDO2AES-256-GCM
PBKDF2Ed25519ES256
TOTPzero-dep crypto
Embedded & Firmware
ESP32-S3TinyUSBUSB OTG
bare-metal Cfirmware
Infrastructure
self-hostedDockerDNS
VPNfirewallreverse proxy
no vendor lock-in
Philosophy
I prefer understanding the mechanism over wrapping a tool. Efficiency is a design goal, not a late optimization. Dependencies are a liability that should be justified, not accumulated.
Constraint-driven design — hardware limits, budget realities, vendor quirks — is part of the problem, not an inconvenience to route around.