Backend engineer. Computer Engineering @ TIET Patiala.
I build systems from scratch — to understand how things work at execution level.
- Backend engineering and system design
- Compilers, execution models, and low-level systems
- How things actually behave at runtime — not just what the docs say
ORION — WebAssembly Compiler
TypeScript · compiler · wasm · binary
Compiles a custom low-level language directly into raw WebAssembly binary modules. No toolchain wrappers, no WAT intermediate — byte by byte, from scratch. Built to understand what actually lives inside a .wasm file.
benz — Graph Query Execution Engine
Go · execution model · graph · volcano
An in-memory graph query engine with a lazy, pull-based Volcano-style execution model — the same architecture behind real query engines. Built to answer the question: how does a traversal pipeline actually pull data through itself?
gosearch — Blazing-Fast CLI Search Tool
Go · cli · concurrency · systems
A concurrent code search tool that pipelines file traversal, I/O, and pattern matching across 4 parallel stages. Respects .gitignore, scales workers dynamically, outputs JSON, and benchmarks at ~1.2ms over 10k files. Zero dependencies.
gosearch -i "error" ./src
gosearch -regex "func\s+\w+\(" .
gosearch -format json "config" . | jq '.matches'kilo — Terminal Text Editor in C
C · raw terminal · systems · zero deps
A fully functional terminal text editor in pure C — raw terminal mode, ANSI escape sequences, low-level file I/O. No libraries. No abstractions. Just the metal.
- AI agents and agentic architectures
- Data-driven system design
- Execution behavior of modern runtimes