Samir Adhikari
Systems-Minded Full Stack Developer
Developer working across web delivery, backend systems, and lower-level data-structure-heavy programming, with a growing focus on storage engines and systems internals.
Short Manifesto
A systems-minded developer who ships full-stack products, then keeps digging deeper into how data structures, storage, and runtimes work under the hood.
Numbers
13
Projects
20
Tools / Skills
4+
Years
What I Bring
What I work on.
full_stack_delivery
Designing and shipping full-stack applications with Next.js, TypeScript, Express, Flask, and practical deployment pipelines. I like owning the whole path from implementation to production.
backend_systems
Building backend services, APIs, and data flows with an emphasis on correctness, observability, and predictable behavior under real usage.
infra_delivery
Handling deployment and operations with VPS hosting, Nginx, release workflows, and CI/CD so projects do not stop at local development.
data_structures
Exploring indexing, persistence, and storage internals through systems programming in C, including disk-backed data structures and B+ tree design.
Featured Work
A few highlights.
Font Converters
A font conversion utility supporting 8 formats across 56 conversion paths, with batch processing, multi-format export, subsetting, auto-generated CSS, and in-memory processing for privacy.
OWHeroStats
An Overwatch statistics platform with hero pages, map breakdowns, comparison views, and filters across ranks, regions, and time windows. Backed by large-scale scraping with frequent stat refreshes.
Loksewa Tayari App
An exam-preparation platform with subscriptions, practice flows, user progress tracking, and dashboards.
16 Aana Homes
A real-estate platform with property discovery, listing filters, agent workflows, and detailed property pages including EMI calculation and unit conversion. I handled the backend and supported frontend delivery.
Currently Building
Active
B+ tree foundation for a storage engine in C
Right now I am building the B+ tree core in C first, working through node layout, structural operations, range traversal, and the persistence groundwork that will lead into disk-backed pages and WAL.
Selected Story
I've spent the last few years shipping real web products across TypeScript, Express, Flask, Django, Next.js, VPS deployments, Nginx, and CI/CD. That work taught me how to own delivery end to end, from implementation to release.
More recently, my attention has shifted toward systems-level programming. I've been building a disk-persistent key-value store in C and working through the invariants and edge cases involved in a B+ tree implementation. That process is where I feel most engaged: careful design, precise behavior, and understanding why a system works, not just that it works.
I still enjoy product work, especially when it involves architecture, backend design, and performance-sensitive logic, but my long-term direction leans toward storage engines, indexing structures, runtime behavior, and low-level correctness.
Working Style
understand_constraints
I start by reducing a problem to its real constraints: invariants, edge cases, expected load, and where correctness actually matters.
model_before_code
Whether it is a web app or a storage structure, I like to model the behavior first so the implementation follows clear rules instead of guesswork.
implement_precisely
I prefer concrete, implementation-level understanding. That means fewer hand-wavy abstractions and more code that behaves predictably under pressure.
verify_reality
I trust explanation only after it survives real behavior: builds, runtime checks, edge cases, and the annoying scenarios that usually expose the truth.