Hello.
I don't guess. I trace, profile, and prove it.
Systems engineer who lives below the abstraction layer. Networking, kernel internals, performance engineering — I write about the things most people hand-wave past.
WHO I AM
From registers and interrupts to APIs and browser pixels — I understand how every layer talks to the next. I choose to live at the core, but I can trace a bug from a user click down to a syscall and back.
Most engineers specialize in a layer and hand-wave the rest. I don't. That's the difference.
Full storyMeasure, don't guess
Opinions are cheap. Flame graphs, traces, and benchmarks are not.
Understand the layer below
You don't own your abstraction until you understand what it hides.
Simple beats clever
The best code is the code the next person can debug at 3 AM.
Cargo-culting best practices
If you can't explain why you're doing it, you're not engineering — you're copying.
Abstraction worship
Wrapping complexity doesn't remove it. Someone has to understand the bottom.
Systems I've built from scratch.
A software TCP/IP stack built entirely in C — Ethernet framing, ARP resolution, IP routing, and TCP state machine via Linux TAP devices. Validates by fetching real HTTP content over the custom stack.
A high-performance thread-safe logging library for C. Per-thread SPSC ring buffers drained by a background logger thread — zero mutex contention on the write path. 15× throughput improvement over naive mutex approach.
A minimalistic 16-bit real mode bootloader in x86 Assembly. Demonstrates BIOS interrupt interface, segment:offset addressing, disk sector loading via INT 0x13, and protected mode transition.
Things I investigated, broke, or figured out.
STILL SCROLLING?