backend developer · Assam, India
Computer Science student building web APIs, Linux tools, and backend systems in Go, Elixir, C, and Python. Interested in operating systems, network protocols, and distributed databases.
I'm an 18-year-old Computer Science student based in Assam, India. I care about writing software that is fast, transparent, and resilient. Rather than relying on black-box abstractions, I like understanding how memory allocators, network sockets, and container runtimes work at the kernel level.
Currently exploring embedded hardware engineering — designing custom circuit boards in KiCad and writing firmware for ARM microcontrollers.
A lightweight container engine built from scratch in Go to dissect Docker internals. Uses Linux namespaces (PID, UTS, mount) and cgroups v2 for resource isolation.
An in-memory key-value database built in Elixir inspired by Redis. Handles non-blocking concurrent reads and writes using OTP processes.
A recursive DNS server written in Go that parses RFC 1035 UDP wire packets directly and resolves domain lookups.
A desktop widget for Wayland Linux environments that intercepts and displays keystroke events in real-time on your status bar.
A slow, command-by-command Arch Linux install for UEFI machines. No archinstall, no skipped steps, and an explanation for the words nobody bothers to define.
Elixir is not a general-purpose upgrade. It is a very good fit for real-time, connection-heavy, failure-tolerant systems. Here is where it is used in production today and where another language is the better call.
WebAssembly is no longer a browser experiment. What changed in 2026, where it beats JavaScript, and how to avoid the boundary cost that kills most first attempts.
One server, ten thousand connections. Why one-thread-per-connection dies, how Go's goroutines and Elixir's BEAM processes survive it, and what I learned building a DNS server in Go and a key-value store in Elixir.
A client told me someone could use AI to build the same thing cheaper. I said here's a subscription, you build it. Why an engineer using AI and a non-technical person using AI produce completely different products.