Hey,
I was always the person who needed to take the machine apart before I believed it worked. Growing up, old electronics, clock radios, and broken hard drives rarely survived in one piece around me. There is still a corner in my room filled with salvaged circuit boards, obsolete cables, and disk platters kept entirely because maybe I'll use this someday. Spoiler: The pile is at the bottom ↓
That same instinct is what pulled me into databases and systems. I wasn't content knowing that an ORM saved a record; I wanted to know where the bytes landed in the write-ahead log, when the OS issued the fsync, and how replica nodes agreed that the write was safe before acknowledging the client.
I want to know how it fails before I trust how it works.
I overthink. Perfectionism in engineering is a strange curse: It keeps you awake at 2am reading kernel manpages because a latency spike was 15 milliseconds instead of 5, but it also means when production catches fire, your recovery path was already tested three times. Yes, I test failovers for fun.
Outside of terminal windows and distributed traces, I love long walks without headphones, strong filter coffee, and deep, quiet conversations about life, philosophy, and where technology is going. I appreciate craft in anything: Woodcarving, typography, mechanical watches, and cleanly written code.
The best systems are built by people who remember that real humans are at the other end of the wire.
If you've made it this far, thank you truly for reading.
This is me, or at least the parts I've uncovered so far.
Divyanshu