I'm a third-year CS student at PES University who's really into systems programming, performance engineering, and building things that run fast.
Currently exploring low-level networking, eBPF, and OS internals while trying to figure out why things are slow (and then making them faster).
🔥 High-performance systems:
- Auction Server - Custom binary protocol over TCP + Redis Lua scripts achieving 650k+ RPM (10,836 RPS). Beat Python baseline by 4.6x by ditching the GIL entirely.
- eBPF Network Monitor - Kernel-space packet analysis processing 1M+ events/sec. Built with Go + C to monitor packet drops and network events with minimal overhead.
⚡ OS Development:
- PicOS - Preemptive multitasking OS for RP2040 (dual-core ARM Cortex-M0+). Built hardware context switching, Round-Robin scheduling, and dynamic program loading with PIC. No firmware reflashing needed.
🌐 Real-time collaboration:
- CodeCast - Live code broadcasting platform with Socket.io. Solved distributed state sync across multiple clients with independent navigation. Won 2nd place at CIE Ignite (top 0.5% of 461 teams).
📊 Full-stack work:
- Internship Tracker - Flask + MySQL + React platform with role-based workflows, REST APIs, and transactional operations using stored procedures.
- Teaching Assistant for Computer Networks at PES University (Socket programming, Wireshark, TCP/IP deep dives)
- Co-founding CodeCast and scaling it beyond alpha
- Writing about systems programming on dev.to
- Probably debugging something that should be working but isn't
I write about systems, performance, and the weird things I discover while building:
- eBPF series - Deep dives into building eBPF-based monitoring tools
- Auction Server breakdown - How I debugged TCP stack saturation and achieved 650k+ RPM
- More technical posts on dev.to
Systems & Performance: Go, C, eBPF, Zig
Tooling: Linux perf, Go pprof, Docker, Prometheus
Web stuff when needed: React, Node.js, Flask, Socket.io
Low-level libraries: cilium/ebpf, libbpf, unsafe, sync/atomic
- Performance: If it's slow, I want to know why
- Systems internals: Kernel-space, networking stacks, concurrency primitives
- First principles: Understanding how things actually work under the hood
- Writing code that doesn't just work, but works efficiently
- 📧 prachijha1805@gmail.com
- 📱 Drop me a message if you want to talk about systems, performance debugging, or why Go's goroutines are actually pretty cool
"Premature optimization is the root of all evil, but knowing when to optimize is the root of all performance."