Full-stack build
Idea to deployed product. API design, data modelling, auth, caching and the frontend that sits on top — shipped on Vercel or a plain Linux box behind Caddy, whichever the project actually needs.
Next.jsExpressMongoDBRedisDocker
Shipped projects · not sketches
transform: translateX(0px)shape: graph
1arr = [5, 2, 9, 1, 6]
2n = len(arr)
3for i in range(n):
4 for j in range(n - i - 1):
5 if arr[j] > arr[j + 1]:
6 arr[j], arr[j+1] = arr[j+1], arr[j]
load the array01/17
VS Code ExtensionCScout
C++TypeScriptVS Code API
Team Project · MLGeospatial Risk Mapping
PythonJupyterLSTMGANReact
TSNXEXRDAI
REVINDPYJVC++
NXTS3JSGLTW
C++TSVS
NXRERXEXMGFB
PYJPMLREVI
An AI platform that generates dependency graphs of GitHub repositories, so a developer can understand an unfamiliar codebase quickly.
An internal retrieval API feeds the model only the files connected through imports and function relationships — cutting token usage and inference cost while improving accuracy. An issue-mapping system surfaces the files relevant to a given GitHub issue.
- GitHub stars
- 52
- Month one
- 744 visitors · 1,127 views
Runs your code in Python, Java or C++ and captures a full step-by-step trace, then renders the visualization that matches the data structure it found.
Traces come from sys.settrace, the Java Debug Interface and gdb. A React/Vite frontend talks to a Node gateway that fans out to three language workers, with a timeline scrubber, play/pause/speed and a key-steps-only mode.
- Content
- 70+ articles · 40+ visualizations
- Infra
- Linux VM · Caddy · pm2
A single scrolling page with a WebGL hero, a pinned project carousel, and live product demos in place of screenshots.
No animation library — the inertial scroll, reveals and pinned carousel are hand-rolled. The hero is a point cloud morphing between generated forms and a portrait sampled from a photograph.
- Dependencies
- No animation library
- Accessibility
- Reduced-motion aware
Brings CScout static analysis into VS Code, replacing the hard-to-navigate HTML it generates by default.
Explore identifiers, dependencies, call graphs and include hierarchies across large C/C++ codebases without leaving the editor — the analysis runs where the code is already open.
- Target
- Large C/C++ codebases
A fashion and clothing storefront with the full commercial path built out — authentication, cart and wishlist, payments, order tracking and an admin dashboard.
Next.js and React on the front with Redux Toolkit for state and Firebase for auth, over an Express and MongoDB API. Razorpay handles payments; the Shiprocket API drives real-time order tracking.
- Payments
- Razorpay
- Fulfilment
- Shiprocket tracking
A team project mapping geospatial disease risk, pairing sequence models over time with a browser client for exploring the predictions.
Python pipelines carry the modelling — an LSTM stage over temporal sequences, a GAN stage for augmentation, SMOTE for class imbalance — served to a Vite and React client through a Python API.
- Role
- Team project
- Modelling
- LSTM · GAN · SMOTE
01 / 06 · Developer Tooling
“The work first, the interface in retreat.”
Frontend engineering
Interfaces that hold up under real data. Considered type, motion that earns its place, and the accessibility and performance work that usually gets skipped.
ReactTypeScriptTailwindThree.js
Developer tooling
The work I keep coming back to: static analysis, runtime tracing, dependency graphs, editor extensions. Tools that make a large unfamiliar codebase legible.
C++VS Code APINodeGraph analysis
04 · About
“From a rough idea to something deployed that people use.”
I'm a computer science student in Noida who builds software end to end. Most of what I make is developer tooling — dependency graphs, execution tracers, editor extensions — the kind of thing that makes a large unfamiliar codebase legible.
I work mainly in TypeScript, React and Node, with a C++ background that keeps pulling me back toward systems work. I care about taking a problem from a rough idea to something deployed that people actually use, and about the parts that usually get skipped: performance, accessibility, and knowing when motion earns its place.
Stack14 — technologies
- 01C++
- 02TypeScript
- 03JavaScript
- 04React
- 05Next.js
- 06Node
- 07Express
- 08Tailwind
- 09MongoDB
- 10Redis
- 11Python
- 12SQL
- 13Docker
- 14Git