Most of what's above lives on servers. This part you can touch.
A display case you talk to by pointing. Hold a finger over an object for three seconds and its story plays in the headphones, while the screen under the glass glows beneath it. No buttons, no touchscreen: a camera above the case watches for your finger, and a passing hand does nothing.
Questions I'm chasing that don't have answers yet.
When a small computer runs a machine, some jobs can't be late: a motor controller has to answer on time, every time. I'm testing whether a different way of letting urgent jobs cut the line makes that timing steadier on a Raspberry Pi, compared with the tricks people already use.
Picture a huge family tree or folder structure that lots of people change at once. DomLock is an existing way to let them work without stepping on each other. I'm studying how to apply many changes together in one batch, safely, while the shape of the tree itself keeps changing.
Lots of software keeps a running list and constantly asks "what's next?", like a server tracking which connections have timed out. The standard tool for this uses a clever shortcut that's usually faster. I found a pattern where it gets over five times slower, and it's the pattern those servers actually create. I'm working out exactly why.
I like building interactive things, but not everyone has time to explore a portfolio. Here is the short version:
Implemented a trusted connection-pool path so designated administrative and monitoring clients can still connect when maxclients is exhausted, avoiding an operational deadlock during incidents.
Added lifecycle-management APIs for explicit goroutine shutdown in long-running controller processes. Also shortlisted for a CNCF LFX mentorship project around LRU eviction for native Helm providers.
I'm Vanshika, a CS student who likes the part of software where tradeoffs are real: concurrency, databases, systems performance, observability, and infrastructure.
I study Computer Science at BITS Pilani (B.Sc., expected 2029) and am based in Bengaluru, India.
I learn best by building close to the metal, measuring behaviour, finding the failure mode, and then making the design simpler. I'm currently looking to grow through systems-oriented internships, open source, and carefully scoped engineering work.