developing the obv
I'm mildly obsessed with the idea that most software has too many dependencies and too little control. So I started building the layer underneath - the networking, the databases, the parts nobody thinks about until they break.
I like problems where "it works" isn't the finish line - where you also need to know why it works, what happens when the network lies to you, or what breaks first under load. That's led me down a lot of rabbit holes: kernel-level packet tunneling, on-device ML, and enough small self-hosted tools that I've basically become my own IT department.
If it involves networking, databases, or an excuse to avoid a dependency, I've probably already built it - right alongside an unreasonable number of small tools nobody asked for.
That said, code is the part of my life I happen to be good at, not the whole of it. I build things because it's genuinely fun, not because I'm chasing a personality around a GitHub graph. Based in the Himalayas, which does wonders for perspective when your code doesn't compile.
Hackathon AI supply-chain platform; built backend hazard logic and mobile integration.
DPI-resistant VPN tunnel, built in both Rust and Go with different evasion strategies.
Self-hosted network diagnostics platform built to get honest bandwidth and jitter numbers, no compression tricks inflating the result.
Distributed key-value store implementing Raft consensus from scratch, verified against a chaos harness that kills nodes mid-write.
87 MB/s peer-to-peer LAN file transfer with zero cloud dependency.
A grab-bag of self-contained utilities: cloud pipelines, a URL shortener, solvers, and snake.
© 2026 Dharmanshu Kumar
Dharmanshu Kumar
developing the obv
Database architecture & low-level networking systems.
Best experienced on desktop for full ASCII rendering engine.