Open to interesting problems
The interesting part is always underneath.
I work on the machinery under other people's features: what runs the job, what moves the data, what holds when the load stops being reasonable. Go most days, TypeScript when the screen needs me, and whatever the other end of the problem happens to be written in.
0+
Years shipping
0+
Jobs on one engine
0%
Peak memory cut
0
Languages, one feature
Now
buildingHestia, so a few coding agents can work on one feature without reading each other's mail.
shippingStreaming intake for very large test plans, so parsing one stops costing a gigabyte of memory.
learningWriting my own skills, subagents and workflows for Claude Code, so a session starts with the conventions already loaded instead of rediscovering them.
Write it down first
A page of trade-offs before the branch saves a week of untangling after.
Follow it to production
Schema, service, manifests, the flag that turns it on. Merged is not shipped.
Assume it dies halfway
Long work needs an answer for the half-finished case, not just the happy one.
Experience
Skills & toolkit
Languages
GoTypeScriptPythonSQL
Backend
NestJSExpressGo-ChiREST APIs
Infra
KubernetesDockerKafkaRedisAWS
Frontend
ReactNext.jsReduxAngular
Side quests
Education
BITS Pilani, Goa Campus
BE, Electronics and Communication
Delhi Public School, Patna
School
Uses
Editor
VS Code · Claude CodeShell
zsh on macOSMachine
MacBook ProDaily drivers
Go · TypeScriptElsewhere
GitHub · resonantChaos22LinkedIn · shreyash2201Architecting with Google Compute Engine