╔═══════════════════════════════════════════════════════════════╗
║ ║
║ still figuring it out, one byte at a time ║
║ ║
╚═══════════════════════════════════════════════════════════════╝
Distributed Systems · Low-Level Systems ·
I’m a systems engineer who loves getting close to the hardware — building and understanding the infrastructure that keeps data safe at scale. I believe the best way to grow is to question abstractions and read source code. So that’s what I spend a lot of my time doing.
“What happens underneath?”
When a database/System behaves unexpectedly, I want to trace it through the system, the block layer, and the hardware. This curiosity has led me to spend weekends reading kernel code, experimenting with weird I/O patterns, and breaking things just to see how they fall apart.
There’s always more to learn — and that’s exactly what makes this field exciting.
If you’re into storage internals, systems architecture, or just want to chat about the Linux kernel, I’d love to hear from you. Reach out on LinkedIn or email.